Conversation
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
If this PR is not desired, let me know and I will close it |
|
|
||
| include /config/nginx/proxy.conf; | ||
| include /config/nginx/resolver.conf; | ||
| proxy_pass http://salt-rim:8080/; |
There was a problem hiding this comment.
Please follow the established set $upstream_{app,port,proto} scheme. as well as spaces over tabs
|
I am no longer running this app in a swag environment so cannot test the requested changes. Initially, I was unable to get it working with the |
3 participants
Description
Add sample proxy config for Bar Assistant
Note: For some reason, this config did not work when using the typical
setdirectives as other configs use. Only passing the proxy address directly worked appropriately.Benefits of this PR and context
With three services running as seperate subfolder locations under the same subdomain, this app suggests deploy its own simple nginx to proxy. This config allows a user to put the services behind their existing SWAG service.
saltrim.subdomain.conf.samplealready exists, but simply points to the simple nginx proxy that the developer documents resulting in a double proxy situation. This submission consolidates the double proxy implementation into a single SWAG config that handles the individual paths.How Has This Been Tested?
Tested on a new setup and another user tested as well in existing environment
Source / References