05-22-2022, 08:09 AM
Every developer will have its own preference concerning a development environment.
The one I prefer:
In this way you will have optimal rich editor performance, while havinge the code, repo and execute commands on the pi.
A pi 4 with will be more then enough 4GB.
Volumio Fusion generates from several template parts a new camilladsp configuration, so it will not require any deep integration into moOde.
That' why you could consider the following suggestion for implementing Volumio Fusion for moOde:
Among others this has the following benefits:
The one I prefer:
- A network share from central file server with a linux friendly file system (like NFS).
- The share is mounted on the several test targets (either multiple physical, or sd switched after reboot).
- Use Visual Code on my host (Win, Linux or Mac) and let it use the VC remote server for development on the target (Pi).
(for example see article like https://www.raspberrypi.com/news/coding-...udio-code/).
- Use the gulp deploy command to go from a source tree to test environment
In this way you will have optimal rich editor performance, while havinge the code, repo and execute commands on the pi.
A pi 4 with will be more then enough 4GB.
Volumio Fusion generates from several template parts a new camilladsp configuration, so it will not require any deep integration into moOde.
That' why you could consider the following suggestion for implementing Volumio Fusion for moOde:
- Make it a standalone web applications or integrate it in the already existing web gui from CamillaDSP it self.
Among others this has the following benefits:
- Befor testing, you can develop it initially on whatever your host is.
- You can use a more modern toolchain (like with CamillaDSP gui python backend and react frontend).
- More people will benefit from it, because you can use it on every platform where CamillaDSP runs.
- No deep integration required into the moode code tree, which eases maintenance.
