nginx-proxy VS lando

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.

If you want to experiment on your own, you can easily spin up a simple LEMP stack with MAMP or XAMPP in a few clicks, and then configure each service to your liking.

I don't think there is any business value in maintaining a site that way for a small biz, but there's certainly educational value. But can't you do that on your own, with a side project, instead of making your company's production website reliant on it?

If you really don't want to do that, sure, you can still roll your own and either just deploy the whole thing as-is (uploading files and mirroring DBs, etc.) or containerizing it with Docker. For making a reproducible LEMP stack that can be easily transferred to another host, also consider the free tool Lando: https://lando.dev/

Still remember https://lando.dev/ ?

I see folks recommending Docker and DDev, which are fine options from my experience, but I also wanted to mention Lando. The team I'm on recently adopted it as part of moving our WordPress network to something deployable, and it has gone pretty smoothly.

Learn about lando.dev (docker container recipes) and how you can run pantheon configured drupal apps on your workstation with it.

Here at Jüssi, we use Docker and Lando as a solution for local development environments and manage Drupal's configurations via Composer. Therefore, we use the 'lando' command as a prefix in the commands below.

Lando (which runs on Docker), which runs on Windows 10 (work) or 11 (home) on WSL2.

https://lando.dev/ — Local environment with recipes and docker.

I'm surprised nobody has mentioned Lando. It uses docker/docker compose under the hood, but adds a further layer of abstraction to make it even easier. Comes with base recipes out of the box for Drupal/WordPress/etc.

Lando, https://lando.dev, has support for pull/push to some hosts.

The most popular is https://ddev.com. Lots of people also use https://lando.dev. I'm old-school, so I tend to use https://www.mamp.info/en/mamp/mac/