WaaromZoMoeilijk/rpi-audio

Scripting design

WaaromZoMoeilijk opened this issue · 2 comments

Aim to place most commonly used or commonly changed defines at the top, perhaps in one separate script. Then derived quantities or less frequently changed values can appear further down
Absolute security isn't absolutely critical here. Maybe the main user is considered a sudo/admin and so automatically has access to a device, say for example in the audio group. However, using groups for permissions instead of root can help

All dynamic content will reside in lib.sh

System user setup per lib.sh settings
Will need to implement adding above user to the audio group.