WaaromZoMoeilijk
commented
3 years ago My vision here is to:
Have an image that performs an automated install up on startup if its the first boot and then clone the git repo locally & execute the install script. This will setup all the cronjob/services/packages we'll need and will also include a daily/weekly git pull to update the scripts. As for the OS I plan to setup unattended-upgrades. Dietpi also includes Dietpi-upgrade which upgrades the OS and DietPI, all with a nice whiptail menu. If this is all done we can have something displayed on HDMI for example saying that the installation is done.
Now from here on we can implement the automated git pull, or not, but that would be the only option needed to update the "audio application" and then separately the OS is done automatically (perhaps only security updates).
No rebuilding of images is needed in this scenario and its portable to more devices. DietPi.txt included in /boot/ will contain the config parameters for the automated instillation and also the install script to run of off the git repo. This way you can take any Dietpi Image, even a 64 bit VM, or other SBC and add DietPi.txt (custom one created for this project) and after a few minutes you'll have a working device no matter the brand.
If you want i can show it in action on another project.
If deploying, installing, provisioning, or updating involves some standard process (like building an image on an independent Linux server with qemu), feel free to hint at an external guide or web page that explains the process so that I'm familiar. I don't imagine many updates would be necessary ultimately, but it will be good information for the initial install and for future projects. Perhaps some distributions keep configuration orthogonal to the binaries and libraries, or a distribution may run from RAM. Basically in this step, speak to what's needed to install the final product. Will the end scripts be untarred somewhere? Provisioned with something like salt? Will it live in a basic container like podman?