nginx-proxy VS Laradock

nginx-proxy becomes almost a must have if you have multiple services and prefer remembering domain names instead of port numbers https://github.com/nginx-proxy/nginx-proxy

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.

Haven’t touched Laravel for years pero baka laradock might be good for your use case

This is a function of the apache configuration files. You should examine those and determine what the issue is, using the xampp gui which will let you edit the httpd.conf file, or whatever it is that xampp uses. xampp provides the default settings you need, so I highly doubt this is the issue, but there is a directive called DirectoryIndex that tells apache what files to search for when a url points to a directory. By default that is going to include index.php. So if that is not working, then there is possibly something else going on with the apache config. To figure this all out you really have to understand how the various possible configuration options work. I don't use xampp so I can't tell you with certainty what the defaults are, but directives like Directory, VirtualHost, DocumentRoot etc, can all be used and combined in different ways to create different outcomes. For example, whether or not an index even appears (in the absence of an index.php) is configurable, as is whether or not you can override settings in a .htaccess file. I'm guessing you might be running xampp under windows, and this is yet another reason why in the era of containers, it's just better to use virtualization or containerization rather than something like xampp. As it sounds like you are still in learning mode, it's not too late to turn your attention to something like docker with https://laradock.io/

It's vastly inferior to laradock and does less.

With https://laradock.io/ it should be no more than a couple of minutes. Yes, this is a development environment and not meant for production. But so is yours, just with a worse approach.

The prime example of what I'm referring to is: https://github.com/laradock/laradock

First, we will use Laravel Sail to run the application locally on our dev environment. There are unofficial Docker environments for Laravel like Laradock but Sail is the official docker dev environment for Laravel. Sail is is a wrapper on top of docker compose.

git clone https://github.com/Laradock/laradock.git