This is a central file (called env.json) to store config that is not checked into version control. It's mounted at /config on the external and internal ports. It's similar in purpose to Heroku's Config Vars.
An example use case: an app that can provide different demos, the config file would be the place to configure which experience it would provide for particular deployment.
I've exposed /opt/radiodan/config over Samba so env.json can be edited without having to ssh into the machine.
In the future we could also extend the setup service to read/write the file.
This is a central file (called
env.json) to store config that is not checked into version control. It's mounted at/configon the external and internal ports. It's similar in purpose to Heroku's Config Vars.An example use case: an app that can provide different demos, the config file would be the place to configure which experience it would provide for particular deployment.
I've exposed
/opt/radiodan/configover Samba soenv.jsoncan be edited without having to ssh into the machine.In the future we could also extend the
setupservice to read/write the file.