You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The script generate_deployment_config and the documentation on production file could be misunderstood.
To be secure by design, usually only the APP server is published to the internet but celery and postgres database should remain on a separate network behind APP.
The deployment config file asks for public ip of database and celery server when invoked.
This could suggest that the server will be directly be reached with a sort of reverse proxy and only running the ansible playbook there is evidence that in case of missing a public ip you should leave that field empty.
The public ip should be left blank if n/a while the private must allways exist.
This apply to inventory file generation.
The text was updated successfully, but these errors were encountered:
The script generate_deployment_config and the documentation on production file could be misunderstood.
To be secure by design, usually only the APP server is published to the internet but celery and postgres database should remain on a separate network behind APP.
The deployment config file asks for public ip of database and celery server when invoked.
This could suggest that the server will be directly be reached with a sort of reverse proxy and only running the ansible playbook there is evidence that in case of missing a public ip you should leave that field empty.
The public ip should be left blank if n/a while the private must allways exist.
This apply to inventory file generation.
The text was updated successfully, but these errors were encountered: