reverse-proxy-confs VS nginx-proxy

More reading: https://github.com/linuxserver/reverse-proxy-confs/tree/master

Linuxserver.io maintains a reverse proxy (SWAG) and they have a github repo of all the configs they support, nextcloud being one of them (ofc to do it on your own you have to merge a few of the includes they have ssl.conf, proxy.conf, etc).

According to this link, guacamole doesn't need an additional base url configuration as it already uses /guacamole by default: https://github.com/linuxserver/reverse-proxy-confs/blob/master/guacamole.subfolder.conf.sample

Glad to see you got it going. For future learning I'd recommend the sample nginx configs built by Linuxserver.io for SWAG, https://github.com/linuxserver/reverse-proxy-confs

Take a basic config, for example https://github.com/linuxserver/reverse-proxy-confs/blob/master/ghost.subdomain.conf.sample

I think swag also templates for those. You can check at https://github.com/linuxserver/reverse-proxy-confs if there is a subdomain conf for it.

Wow, this makes me appreciate linuxserver's mastodon docker so much more. Plug in your parameters and it just works. Linuxserver's swag docker is similarly one click install for nginx/reverse-proxy/certbot. It even comes with a mastodon sample conf.

I have an express API that runs on EC2 and I am using nginx-proxy

If Traefik is not your thing Im happily using https://github.com/nginx-proxy/nginx-proxy and sslip.io for local docker compose development.

And then even plain nginx to proxy to non docker services...

(And ipv6 for really short urls. E.g. `example.com.--1.sslip.io` etc)

I wanted to share with you an exciting new tool that simplifies the process of interacting with the NGINX Proxy Manager API. It's a TypeScript tool that generates API requests based on environment variables within a Docker container. This tool is heavy influenced by the https://github.com/nginx-proxy/nginx-proxy but it works with npm.

I use an automatically configuring reverse proxy - there's several to choose from, but the nginx-docker image is really nice, and comes with another image to do automatic SSL with certbot (if you wanted to host things externally).

Docker runs on the 3B+ so you could use this [Github] or the one I have deployed here [NGINX Proxy Manager site] amongst others.

- and this

docker compose + wildcard dns + reverse proxy that covers all widecard subdomains + https://github.com/nginx-proxy/nginx-proxy (not to be confused with nginx itself) then setup a container for each app and set a subdomain for it, you can add ssl if you have a public domain or use self signed certs (but you need to distribute it to all machines and devices)

setting up letsencrypt with nginx-proxy and acme-companion

We use the nginx-proxy docker image. Auto-configuring reverse proxy with support for certbot. Never been easier - just put your domain and certbot details in your container env, and it does the rest.

I just use the nginx-proxy image, makes it all super easy, auto-configuring, and all domain/cert information is stored against the project rather than the proxy.