Nginx
Reddit take
Not enough linked mention summaries yet; the source excerpts below are the evidence.
Pros
- And they ain't hard; but I would suggest nginx over apache if you have to start learning one.
- What made sense to me back in the day (and still does due to how easy running a server really can) is to use a solid backend language like PHP within a secure and fast server setup like nginx/apache and then simply serve the content.
- NGINX will let me route traffic to :3000 without question...but if I wanted to I could go into the OS I could make sure to deny in or outbound traffic unless I explicitly allow a port
- So, I’m running an unprivileged container where only Nginx (standalone) is running, without a manager. I route all traffic through it.
- I use the built-in one in Proxmox to control access to specific ports on the machines, so for example the only incoming ports I have enable for Nginx are http, https and SSH.
Cons
- Nginx redirection (if you use it) is another option if you dont use cloudflare but it will be slower comparatively as the traffic will hit your server before redirection .
- I will for sure make sure that it runs an up-to-date OS with all security patches installed and will run the latest version of nginx to host it.
- Since it simply provides the .html files based on the vault's .md files, it still needs a static file server (Apache or NGINX) and PHP (for server side processing).
- The only thing I've done as the years have gone by is switch from Apache to Nginx.
- For instance, you can't use it with Nginx because Nginx only supports HTTP/1.1 for upstream connections.
Sentiment
32 positive (78%) · 8 mixed (20%) · 1 negative (2%)
Trust + time weighted score: +77% · raw score 76%
What redditors said (10 of 41)
And they ain't hard; but I would suggest nginx over apache if you have to start learning one.
What made sense to me back in the day (and still does due to how easy running a server really can) is to use a solid backend language like PHP within a secure and fast server setup like nginx/apache and then simply serve the content.
NGINX will let me route traffic to :3000 without question...but if I wanted to I could go into the OS I could make sure to deny in or outbound traffic unless I explicitly allow a port
So, I’m running an unprivileged container where only Nginx (standalone) is running, without a manager. I route all traffic through it.
I use the built-in one in Proxmox to control access to specific ports on the machines, so for example the only incoming ports I have enable for Nginx are http, https and SSH.
Nginx redirection (if you use it) is another option if you dont use cloudflare but it will be slower comparatively as the traffic will hit your server before redirection .
to each static droplet the static-app was deployed that served a few static assets using Nginx.
Tech stack: Leaning toward Docker containers with nginx as reverse proxy. Good starting point or would you recommend differently?
Get a Mini PC, install Proxmox, run a few things that don't need that much space like a Spotify alternative (Navidrome), start page replacement (Prompt), Caddy/Nginx for a reverse proxy
You also need to make sure your domain isnt empty to protect yourself against active probing. This is achieved with NGINX.