Hi balena family,
There has been lots of discussion going on around different development and testing workflows. It is a difficult one to fix with only one solution because there are so many different ways to develop, and languages to develop in.
Based on some of the different conversations going on around the forums, I thought I would push an NFS-Server option to the Hub, that allows mounting a folder from your device to your local computer (your Mac for example). It allows you to edit on-device code as if it were on your local computer. Then you simply run the command on the device to test it in the balena device environment without having to keep pushing or rebuilding the container.
It’s certainly not a solution for all the different workflows, but I have been using it the last week when working in Python and it has proved quite useful. It isn’t an officially supported solution, just another community approach to discuss and try to understand how the different development workflows can evolve.
It would be great to hear ideas on other workflows to make development easier, both related to this NFS approach and other ideas too.
Shout out to Volkov Labs who found this effective method of running NFS servers and clients on device and put together the solution for sharing mounts between containers: balenaHub: an easier way to find and publish fleets, apps, and blocks for edge devices