Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

public vs private ips when setting group_vars #787

Open
paolantoni opened this issue May 29, 2019 · 0 comments
Open

public vs private ips when setting group_vars #787

paolantoni opened this issue May 29, 2019 · 0 comments

Comments

@paolantoni
Copy link

paolantoni commented May 29, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant