Hello wonderful community, new user here
First of all, this ecosystem is awesome! The fact I can configure my Raspberry Pi remotely, use a
git push and deploy the services I want is an awesome experience. I’m super satisfied .
I’m about to sail on the adventure of designing my dream sound system. I’m using balena-sound as a starting point, and I have a few hardware / firmware related tweaks I’d like to set. Planning how to deploy these changes made me a bit confused about the multi containers paradigm.
What’s bothering me is that I want multiple services / containers to access the hardware, and ideally, all of these services should have the same sound related settings, including running the same
On the balena-sound project, the
spotify are separate services, and they all share eventually the same hardware, but run in different containers. What happens if during a spotify song, someone connects to the device via bluetooth? How would the spotify service know it needs to stop?
Say I have some firmware files I’d like to install on my system (I need these files). Additionally, I want to run a certain
amixer command on startup. I tend to think, contrary to the balena-sound project that it’d be best to define a single container for all processes that use the sound hardware. Is it a bad beginner’s choice?