nginx-proxy VS homepage

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.

It's Homepage. It's great for dashboarding, but has a few shortcomings in that you need to secure it behind a reverse proxy, otherwise you'll end up leaking credentials to the whole internet, unless you abstain from using its "connectors".

I use dietpi as os, the dash board is from homepage

I use Homepage. Has integrations with nearly every service I use and it's pretty easy to set up

Step 2. Build a Dashboard. There are many options for personal dashboards, but I run Ben Phelps' Homepage in a Docker container. It is fast and simple to configure with YAML files. Here is a screenshot of my home dashboard. Homepage has more features than I use. Any ports needed for your services will be added to the URLs in the Homepage config file. Then, all you need to do is create a bookmark to Homepage in your partner's browser.

Good to see a dashboard post here that isnt just using Homepage :)

The control panel is called Homepage. I like it more than Heimdall. To manage Docker I use Portainer.