Add molecule setup for mirsg.infrastructure.nginx
#50
Assignees
Comments
p-j-smith
added a commit
that referenced
this issue
Jan 19, 2024
Fixes #50 FIxes #51 Fixes #52 - add option to use own template for the nginx configuration (the template to be used can be selected using the `nginx_conf_template` variable). Define one template: 1. a template for configuring nginx as a reverse proxy for XNAT with an optional additional default server (`nginx_reverse_proxy.j2`). A default server is created if `nginx_add_default_server` is `true` - use flat variable naming for the nginx role rather than nested - update `mirsg.infrastructure.install_xnat` group vars with new variable names. At the inventory level if `nginx_use_ssl: true`, we will need to set: - `nginx_server_cert_cache: ssl.server_cert` - `nginx_server_key_cache: ssl.server_key` - add a molecule configuration for `mirsg.infrastructure.nginx`. This configures nginx as a reverse proxy for a Flask app running on a Gunicorn server. Include a verify playbook to check we can connect to the server from the localhost via nginx - fix the molecule configuration for `mirsg.infrastructure.install_xnat` - the tomcat port was being published rather than the one for http connections, so nginx wasn't being used to connect from localhost even though it was configured. Add a verify playbook to check we can connect to the server from the localhost via nginx - add a workflow to run molecule test on the nginx role - add a role README --------- Co-authored-by: Daniel Matthews <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: