A collection of stuff for my servers.
- Create the
swag-containers
network so that your containers can communicate with each other
docker network create --driver=bridge swag-containers
-
Modify
swag/run.sh
to only include theSUBDOMAINS
you want.- If you want to update them, edit
swag/run.sh
and then runswag/update.sh
- For all confs under
swag/config/nginx/proxy-confs
orswag/config/nginx/site-confs
that you do not want, append.sample
to the filename.
- If you want to update them, edit
-
Run
swag/run.sh
-
Spin up whatever other apps you want to run!
For each new reverse proxy, follow these steps:
- Create a new proxy-conf in
swag/config/nginx/proxy-confs
- Do this by copying your confs from
swag/config/nginx/proxy-confs/subdomains
toswag/config/nginx/proxy-confs
- Do this by copying your confs from
- Update the
SUBDOMAINS
env variable inswag/run.sh
to include the subdomain of your service - Create a CNAME entry in your domain manager:
CNAME <container name>.<domain>.net <domain>.duckdns.org
If you run into 502s, read: https://docs.linuxserver.io/general/swag#502
- In most cases the contents of
/config/nginx/resolver.conf
; should beresolver 127.0.0.11 valid=30s;
, if this is not the case, you can delete it, and restart the container to have it regenerate.