It would be greater if it can also leverage IPFS. So we can have unique identifiers per media object and hence deduplication in a P2P network which in my opinion is more federvise affinitive. I have been thinking of making such an alternative media backend for a while.
qazwsxedcrfv000
joined 2 years ago
If your dynamic pages leverage PHP, Nginx can be configured to support that via FastCGI. If your site has its own server runtime (e.g. a site written with NodeJS or Go), Nginx reverse proxy is literally its strength. So yeah give Nginx a try. I bet you won't regret it.
I think the question is if you want to add the external USB hard drives to Proxmox so that not just the mentioned Ubuntu VM but other VMs and LXCs can benefit from them or if you want them to be added exclusively to the Ubuntu VM and Ubuntu VM only.
If it is the latter, you can leverage USB device passthrough and passthrough the two drives to the VM in whole. Then you can do whatever you want with them inside the VM. You can use ZFS or BTRFS or mdadm to create a stripe aka RAID 0 config.
Indeed ZFS has support for stripe (RAID0 like) ~~vdev~~ zpool since very early days.
Is your site static or dynamic? If your site is made of good old HTML and CSS or your site is a SPA, any web server will serve it well.
I prefer Nginx as it is performant and versatile enough for most use cases.
If you, as the sole user, are not subscribing to dozens if not hundreds of communities, 1GB should be barely okay. As others have pointed out, it is storage that requires more attention with a Pi 4B.
There was a 1GB model at launch. The Pi foundation discontinued it when they dropped the price of the 2GB model.
The tech behind Outline Shadowsocks is solid. It establishes a private tunnel to your server in the free world and attempts to obfuscate the traffic as much as possible. The project is not really abandoned. There are still continuous development/maintenance activities in the repo.
Wireguard does not intentionally obfuscate its traffic. If the said authoritarian country has invested in deep packet inspection, the traffic can be easily flagged and retarded.
I am not sure if Immich supports configuring base URL. You can look into that.
If it is not supported, you may need to try your luck with URL rewriting. Nginx can do it natively. Briefly, you need to configure Nginx to strip the /immich from the request URL before proxying the request to the Immich instance.
The simplest way is to add a Basic auth to the
lemmy-ui, say via the reverse proxy.