At the moment a server reboot or starting some services using ./start.sh will not start the admin and postgis services, as these rely on Ansible environment settings. A repeatable mechanism is needed.
Idea is as follows:
populate a dictionary of env-variables in Ansible vars.yml (encrypted with Ansible Vault)
propagate these to /etc/environment on server host at bootstrap and deploy actions/playbooks
use these vars in docker-compose environment (files) like ghc.env
justb4
commented
3 years ago
At the moment a server reboot or starting some services using
./start.shwill not start theadminandpostgisservices, as these rely on Ansibleenvironmentsettings. A repeatable mechanism is needed.Idea is as follows:
vars.yml(encrypted with Ansible Vault)/etc/environmenton server host at bootstrap and deploy actions/playbooksdocker-composeenvironment (files) like ghc.env