C#
eh... those are fundamentally different, C is not object-oriented so OOD part goes straight out of the window. The only thing similar about them is syntax to some degree (which is really irrelevant), approach is completely different.
reinar
joined 1 year ago
1000 daily visitors
it's not much, any non-micro vps from decent provider will do. For precise recommendations it'd be better to know where most of your users are located, latency is a bitch.
I've updated to 0.18.0 as well and can see your comment
It's not even about gui.
If you want to self host you get yourself a pile of software of community-level quality (i.e "it works good until it doesn't" is the best outcome) you need to care about. This means constantly being involved - updating, maintaining, learning something, etc, and honestly it's time-consuming even for experienced sysadmins.
Generated wireguard config with nat-pmp enabled in ProtonVPN panel, put keys and endpoints to my vpn client (gluetun docker image), used https://github.com/soxfor/qbittorrent-natmap image to interactively update port from qbittorrent settings on proton through natpmpc.
https://github.com/soxfor/qbittorrent-natmap/issues/13 - I've set up my docker-compose pretty much by this example (ignore "unreliability" feedback, OP probably has some issues upstream - image itself is working). If you are using this, remove all upnp/nat-pmp checkboxes from qbittorrent, this image is your nat-pmp client.
Speaking of clients: this setup is for sure extremely ugly, but native implementation of nat-pmp in libtorrent for some reason is not doing what's needed, maybe because qbittorrent tries to use upnp/nat-pmp simultaneously. What I see is an error message from upnp client ("no router found" - understandable) and complete silence from nat-pmp.
They are now refunding past their 30-day money back period if you didn't use cash. Just got a refund for a top-up made in February.
https://lemmy.dbzer0.com/post/21703
I ended up buying ProtonVPN. Port forwarding required a bit of trickery with natpmpc image to set up in my case (headless wireguard gateway for dockerized services), however now it's fine and working.
Speeds are at least 800Mbps download (which is maxing out my uplink, vpn is likely to be capable for more), didn't have a chance to test upload.
They are claiming ProtonVPN port forwarding only works with Windows, however this is only relevant if you are using protonvpn app.
You can still generate wireguard config with nat-pmp support.
https://protonvpn.com/support/port-forwarding-manual-setup/
I'm not interested in their app at all since it's going to run as headless docker gateway for qbittorrent/radarr/sonarr/other shit anyway, but - it seems like they support proper NAT-PMP which is massive.
https://protonvpn.com/support/port-forwarding-manual-setup/
Wow wtf I didn’t know this.
https://mullvad.net/en/blog/2023/5/29/removing-the-support-for-forwarded-ports/
They already disabled the possibility to add new port forwards and will remove any existing ones completely on 1st of July.
it's most likely coming from postgres, db server tends to be the main resource hog.
ramnode or linode will do, you'll need 2+GB of RAM.