github/reverse-proxy-confs
1
0
Fork 0
mirror of https://github.com/linuxserver/reverse-proxy-confs.git synced 2025-08-14 02:27:24 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Format files

Browse source
This commit is contained in:
Eric Nemchik 2023-02-12 20:51:33 -06:00
commit 0eb569982b
16 changed files with 52 additions and 51 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -2,7 +2,7 @@
# How to use these Reverse Proxy Configs
This folder contains sample reverse proxy configs for various docker images linuxserver provides and other commonly used applications.
This folder contains sample reverse proxy configs for various docker images linuxserver provides and other commonly used applications.
NOTE: We avoid providing samples that publicly expose server management software (ex: syno, qnap, unraid, proxmox, esxi, etc). Pull requests to add samples for this category of applications will not be accepted.
@ -23,12 +23,12 @@ Conversely subdomain reverse proxying does not require special accommodation by
Make sure that your default site config contains the following lines in the appropriate spots as seen in the default version:
1) For subfolder methods: `include /config/nginx/proxy-confs/*.subfolder.conf;`
2) For subdomain methods: `include /config/nginx/proxy-confs/*.subdomain.conf;`
1. For subfolder methods: `include /config/nginx/proxy-confs/*.subfolder.conf;`
2. For subdomain methods: `include /config/nginx/proxy-confs/*.subdomain.conf;`
### Ensure you have a custom docker network
These confs assume that the swag container can reach other containers via their dns hostnames (defaults to container name) resolved via docker's internal dns. This is achieved through having the containers attached to the same user defined docker bridge network.
These confs assume that the swag container can reach other containers via their dns hostnames (defaults to container name) resolved via docker's internal dns. This is achieved through having the containers attached to the same user defined docker bridge network.
- If you are using docker-compose and the containers are managed through the same yaml file, docker-compose will automatically create a custom network and attach all containers to it. Nothing extra is required.
@ -36,14 +36,14 @@ These confs assume that the swag container can reach other containers via their
- If you are using a gui manager like portainer, you can create a custom bridge network in the gui, and select it when creating a new container.
- If you are using unraid, create a custom network in command line via `docker network create [networkname]`, then go to docker service settings (under advanced) and set the option `Preserve user defined networks:` to `Yes`. Then in each container setting, including the swag container, in the network type dropdown, select `Custom : [networkname]`. This is a necessary step as the bridge network that unraid uses by default does not allow container to container communication.
- If you are using unraid, create a custom network in command line via `docker network create [networkname]`, then go to docker service settings (under advanced) and set the option `Preserve user defined networks:` to `Yes`. Then in each container setting, including the swag container, in the network type dropdown, select `Custom : [networkname]`. This is a necessary step as the bridge network that unraid uses by default does not allow container to container communication.
If the reverse proxied containers are not reachable via dns or they are running on a different machine, you will have to modify these confs to fit your needs.
### Rename the required proxy configs
1) Rename the conf files and remove the `.sample` at the end (ie. `sonarr.subfolder.conf`)
2) Restart the swag container
1. Rename the conf files and remove the `.sample` at the end (ie. `sonarr.subfolder.conf`)
2. Restart the swag container
### Make any necessary changes detailed in the config