Add crude front-end Web router.
This creates a service that listens on (by default) port 80 and maps LOCKSS's many Web interfaces, each listening on a different port, to paths under a single base. For example: http://lockss.test/crawler -> http://lockss.test:24631 This is not ready for production. The remaining tasks are as follows: - Turn the front-end into a proper Docker image and service. (It should include a health check.) - Merge the lockss-config-frontend into the main lockss role. - Remove from the firewall rules access to the other administrative ports that are now accessed through this. - Document the front-end paths. Or, better yet, write a landing page that lists them all.
Showing
- dev.playbook.yml 3 additions, 0 deletionsdev.playbook.yml
- roles/lockss-config-frontend/defaults/main.yml 3 additions, 0 deletionsroles/lockss-config-frontend/defaults/main.yml
- roles/lockss-config-frontend/tasks/main.yml 32 additions, 0 deletionsroles/lockss-config-frontend/tasks/main.yml
- roles/lockss-config-frontend/tasks/main.yml-v_nginx 49 additions, 0 deletionsroles/lockss-config-frontend/tasks/main.yml-v_nginx
- roles/lockss-config-frontend/templates/11-in-lockss-frontend.ferm.j2 3 additions, 0 deletions...s-config-frontend/templates/11-in-lockss-frontend.ferm.j2
- roles/lockss-config-frontend/templates/httpd.conf.j2 114 additions, 0 deletionsroles/lockss-config-frontend/templates/httpd.conf.j2
- roles/lockss-config-frontend/vars/main.yml 26 additions, 0 deletionsroles/lockss-config-frontend/vars/main.yml
Loading
Please register or sign in to comment