So basically… this is a blatant cash grab, and a nearly 200% one depending on the level of service you pay/paid for. Wonder how long it will be before the lifetime pass is discontinued and everyone gets forcibly moved over to a monthly subscription model

A self-hosted photo/video viewer which presents itself as an Open Directory that maps closely to the underlying file system and also includes the ability to view images and stream videos. If videos are too large/incompatible with the user’s browser, they should be transcoded on the fly (optionally with the gpu). Genuinely surprised something like this doesn’t exist

Same, I also use Cloudflare dns, tunnels, and pages. Having these all in the same place makes it easy to deploy/keep track of everything

I use OVH. Reasonable prices, very reliable, and no bandwidth caps

Oh yeah don’t get me wrong I love nicotine+ too! I figured I’d link to slskd since this is the selfhosted community after all 🙃

I’m not a fan of YouTube’s audio compression algorithm (optimized for saving google’s bandwidth but sounds awful on higher fidelity audio setups). If quality is a concern, I can’t recommend slskd enough

I use wiki.js in the linuxserver.io flavor. I have 3 URLs for every service I run: public, LAN, and tailscale url. My “homepage” is a big markdown table with links to all the services. It’s not pretty by any means, but it’s very functional

you can also delete them recursively with

find . -name '*.DS_Store' -type f -print -delete

(adapted from this script)

The pi zero is good for small projects that don’t require a lot of compute, however I personally haven’t found it to be useful in a self-hosted context. Unless you really don’t care about performance, the low specs make it unsuitable for hosting most of the services you listed above

gluetun bundles a control server on port 8000 which you can query for the port number (don’t worry about openvpn being in the url path, it still works with Wireguard). In my bash script (running on the host system), I use curl to retrieve the forwarded port number and then do a POST with that data to the API of my qbt client which is running in another container on port 8080.

There’s a reason why most providers don’t allow that feature anymore

Yes, cheese pizza

It’s said that port forwarding is a security risk

Says who? Assuming a fully patched system/client and a properly configured firewall/network, I’d love to hear more about these “risks”.

Also, qBitTorrent works just fine without it.

Only if you don’t care about seeding

Based. I use gluetun with qbt and ProtonVPN (with port forwarding). Despite this being a tricky config, it was still pretty easy to setup. Can share bash scripts if anyone is interested.

I’m personally a big fan of bore. It’s easy to setup/use and there’s a free public instance operated by the developer.