Draft: config/roles/menshen-frontend/tasks/main.yml - redirect doman/api/* to menshen backend
address : leap/menshen#63
Merge request reports
Activity
changed milestone to %2025.01LEAP VPN Release
added Review Ready label
requested review from @cyberta
assigned to @sgk
58 58 } 59 59 # v3 compatability 60 60 #End-block-apiv3 61 62 - name: Insert block below server_name domain.com; 63 lineinfile: 64 path: /etc/nginx/sites-available/float.conf 65 insertafter: '^\s*server_name\s+{{domain}}' 66 line: | 67 #Begin-block-apiv5 68 # begin block 69 location ^~ /api/ { 70 include /etc/nginx/snippets/block.conf; 71 include /etc/nginx/snippets/proxy.conf; 72 proxy_pass http://be_api_9001_menshen; this is wrt the key here : https://0xacab.org/leap/container-platform/lilypad/-/blob/main/config/services.bitmask.yml?ref_type=heads#L11
renamed menshen to api after deprecating vpnweb here :
Edited by sgk
Apologies for the random pass-by comment but, in case you are interested in avoiding resorting to ansible as much as possible (specially when touching control plane artifacts), I wonder if you were aware that one can set up float services on sub-paths (e.g. /api/ here) with a path attribute on the public_endpoint, like we do here for example: https://git.autistici.org/ai3/config/-/blob/master/services.common.yml?ref_type=heads#L146
added 1 commit
- d7fb2c24 - config/roles/menshen-frontend/tasks/main.yml - redirect doman/api/* to menshen backend