When doing development with the AutoPi, it is possible to do it all through the Cloud.
- Make changes
- Push changes to device
- Restart services
- Execute module
- Go to step 1
But while this process can be used, it is much too slow for actual development. So the Cloud should be used for management and to push out code when the development has finished, and not in the actual development workflow.
Fortunately, there are other much faster alternatives, here are a few ways to do it.
You could instead SSH into the device and edit the files directly. When syncing from the cloud, the modules will be put in the following directories, based on the type:
So you can simply edit/create the files directly, but make sure to avoid clashes with the cloud synced modules, to prevent losing work if you sync the module from the cloud, as that will, without asking, overwrite the file on the device, even if you have made local changes to it.
When you make changes to the files, to make sure that the minion process picks up on the change,
you can either restart the
salt-minion service, or run this command
which reloads the external modules, i.e. your code.
Alternatively, another workflow can be to have a script on your development machine that copies
the files to the device via
scp, that way you can
make the changes in your favorite editor. Remember to have the script also either restart the
minion service or run the
refresh_modules command as noted above. Doing development on the local
machine is preferable for many, and is also the way we do development in office as it has the
benefit of the above solution, but also allows the user to be as productive as possible by in their
preferred development environment.
We hope this helps you get started developing with our device and platform.
Remember that we also offer additional more in-depth paid support to get you started with your project: https://shop.autopi.io/products/development-support-voucher-16/
If you'd like to discuss this topic with us or other fellow community members, you can do so on our community page dedicated for this guide: Local Development Workflow.
You can also write us an email on firstname.lastname@example.org. We usually respond back in 24 hours on working days.