Proxmox VS Caddy

There's no one right way to do this. For me, I focused on isolation and containment. So I used LXCs for everything with Plex as the only Privileged container. All other *arrs remained unprivileged. My data resides on a NAS elsewhere in my network so I had to set up SMB sharing to all the LXCs and as you'll find out, that becomes less than intuitive. I wrote a guide here that details how I configured everything.

I used the lxc script from tteck to set up a new plex installation in a lxc. https://github.com/tteck/Proxmox Installed nfs-common and updated /etc/fstab so I mounted all the media shares from my synology.

The actual scripts: https://github.com/tteck/Proxmox

After poking at a couple of these, they seem like they're 50% shiny packaging and 50% one-liner bash commands.

Then, I tried installing Jellyfin using scripts. That went better than my previous attempt. However, I still could not get the mounted storage to appear on Jellyfin UI. I googled the issue and experimented with several solutions like mounting the storage on the Proxmox server. When I added a new library (using ip), Jellyfin started scanning. it seems like the Jellyfin is doing something because the CPU was running up to ~70%.so, I left it overnight. When I checked in the morning, I still don’t see any videos on Jellyfin UI. I checked the logs and I saw that it threw access denied error to a /proc/, but nothing why it couldn’t display files on the mounted storage. My current setup only has a built in GPU, 1 x 1TB SSD (im looking to add more storage later on) and the mounted storage only has 25 videos ~200-500 MB.

The HA VM took about five minutes, all created by using this script: bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/vm/haos-vm.sh)"

I had an acl issues configuration using NPM on docker ( proxmox > LXC > Docker > NPM) when using IPV6. So now I'm using lxc on unprivileged LXC using this script. https://github.com/tteck/Proxmox

my major issue: I tried to install tailscale on nextcloudpi and it didn't work, even tried to use this command line: bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/misc/add-tailscale-lxc.sh)" -s 106 also didnt work for with nextcloudpi. But Tailscale installed perfectly on NPM.

I set up on proxmox with the help of this. https://github.com/tteck/Proxmox

This github repo is a great place to start with LXCs https://github.com/tteck/Proxmox

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/scrypted.sh)"

No, look at the associated unit test: https://github.com/caddyserver/caddy/blob/c6eb186064091c79f4...

If that test fails we could serve PHP source code instead of having it be evaluated, a major security flaw.

However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:

I think that recompiling with upgraded Go will not solve the issue. It seems Caddy imports `golang.org/x/net/http2` and pins it to v0.22.0 which is vulnerable: https://github.com/caddyserver/caddy/issues/6219#issuecommen....

Caddy [1] is a single binary. It is not minimal, but the size difference is barely noticeable.

serve also comes to mind. If you have node installed, `npx serve .` does exactly that.

There are a few go projects that fit your description, none of them very popular, probably because they end up being a 20-line wrapper around http frameworks just like this one.

[1] https://caddyserver.com/

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

So I dug a little deeper and came across this gem: Caddy. Caddy is this fantastic, extensible, cross-platform, open-source web server that's written in Go. The best part? It comes with automatic HTTPS. It basically condenses all the work our scripts and manual maintenance were doing into just 4-5 lines of config. So, stick around and I'll walk you through how to set up an automatic SSL solution with Caddy, Docker and a Node.js server.

Let's use Caddy which can act as reverse-proxy with automatic HTTPS coverage.

Even if it may be simple, it doesn't handle edge cases such as https://github.com/caddyserver/caddy/issues/1632

I personally would make the trade off of taking on more complexity so that I can have extra compatibility.

One of the most heavily used Russian software projects on the internet https://www.nginx.com/blog/do-svidaniya-igor-thank-you-for-n... but it's only marginally more modern than Apache httpd.

In light of recently announced nginx memory-safety vulnerabilities I'd suggest migrating to Caddy https://caddyserver.com/