From the root directory of your project you have the following sub-commands available:
You can combine the commands together like
clickable build click_build install launch
Runs the default sub-commands specified in the “default” config
Compile and run the app on the desktop.
Generate a new app from a list of app template options.
clickable init -n <app template name>
Generate a new app from an app template by name.
Opens a shell on the device via ssh. This is similar to the
Kills a running process (specified by the config). Using this you can relaunch your app.
Cleans out the build dir.
Builds the project using the specified template, build dir, and build commands.
Takes the built files and compiles them into a click package (you can find it in the build dir).
clickable click-build --output=/path/to/some/diretory
Takes the built files and compiles them into a click package, outputting the
compiled click to the directory specified by
Takes the built click package and runs click-review against it. This allows you to review your click without installing click-review on you computer.
Takes a built click package and installs it on a device.
clickable install --click ./path/to/click/app.click
Installs the specified click package on the device
Launches the app on a device.
clickable launch --app <app name>
Launches the specified app on a device.
Follow the apps log file on the device.
clickable run "some command"¶
Runs an arbitrary command in the clickable container.
Configure docker for use with clickable.
Update the docker container for use with clickable.
Turns on the device’s display and keeps it on until you hit CTRL+C.
Turns off the device’s display timeout.
Lists the serial numbers and model names for attached devices. Useful when
multiple devices are attached and you need to know what to use for the
clickable <custom command>¶
Runs a custom command specified in the “scripts” config
clickable <custom command> --device¶
Runs a custom command specified in the “scripts” config on the device.
clickable <any command> --container-mode¶
Runs all builds commands on the current machine and not in a container. This is useful from running clickable from within a container.
clickable --desktop --nvidia¶
Use clickable’s desktop mode with proprietary Nvidia drivers. This requires nvidia-docker to be installed and setup. Please note, only version 1 of nvidia-docker is supported at this time (version 2 does not support OpenGL).