You could port forward.

However, I’d buy a digital droplet for 10 USD a month, point the A record of the domain to that and then use Caddy to implement SSL.

Caddy can run a http server or reverse proxy something on localhost.

Debugging large code bases.

Sometimes it catches it, sometimes it does not.

Tedious work otherwise and a real time saver overall

You should check out Netflix :p

A collection of programs that will track your media directory and automatically start a torrent on a missing piece of media with a web interface that you can use to browse what you do and do not have.

• lidarr – music manager
• radarr – movie manager
• sonarr – tv shows manager
• prowlarr – torrent index manager (ie tell sonarr to check thepiratebay.

So you basically start these programs, connect them with prowlarr so that they can find torrents, point them to a media directory, and then connect that back to a torrent client such as Qbittorrent. When a new TV show comes out, they will automatically download that into your downloads directory and hardlink it to your media directory, torrent keeps seeding, it’s filed away properly and no extra storage use until the hardlink breaks. So if you also have Jellyfin / navidrome pointing at your media directory, you will just see new media pop up each week.

I recommend using qbitorrent in a docker container that enforces a vpn, then you can just drop a WireGuard profile in there. AirVPN Works well for this as it supports port forwarding as well.

I personally manage the entire thing in a single docker compose file, and that’s what I would recommend, because then it’s set and forget.

They don’t need necessarily need a Usenet account, They can work perfectly well with ordinary torrents.

Openrc is used by alpine and gentoo. They both work great.

Runit used by void is also fine.

If you can figure out gentoo it’s not a bad OS but compiling can be slow. You’ll learn a lot though. Checkout oddlama/gentoo-installer

You can’t, this guy doesn’t know what he’s taking about.

Port forward behind CGNAT won’t get you out. Best bet here would be ipv6.

Tor would work. However, only over Tor obviously.

That’s right, one should. However, I’m using this only as an internal documentation tool, There’s no port forward and it’s not public. I am literally using it to take notes on a few things I’m developing.

It’s actually really nice being able to drop a whole bunch of links and have them threaded and linked between each other. It works quite well.

Yeah, without a doubt, it’s just an oversight.

There’s nothing malicious here.

I should have read the docker compose a bit closer when I was trying to figure it out but There’s only so many hours in the day, and sometimes you rush.

In not the OP but I hit the same issue.

Yeah this hit me as well and it was very confusing until I found that lemmy.ml

I can’t find it on the main branch so I didn’t raise am issue

Click the link, you’ll see it is indeed the first heading under Criticism

Set up wireguard in a docker container and then forward the port to wireguard, the default container on docker hub is fairly straightforward and you can always ask me for help if you need :).

However, If you are using ipv4, you need to make sure that you’re not behind a CG-NAT (If you think you might be, call your ISP and tell them you have security cameras that need to get out or something like that).

You could also try tailscale which is built using wireguard with nat-busting features and a bit easier to configure (I dont personally use it as wireguard is sufficient for me).

After that Caddy + DNSMasq will simply allow you to map different URLs to IP addresses

• dnsmasq
  • will let you map, E.g. my_computer -> 192.168.1.64
• Caddy (Or nginx, but caddy is simpler)
  • will let you map to ports so e.g.:
    • with DNS (DNSMasq as above)
      • http://dokuwiki.my_computer -> http://my_computer:8080
    • Without DNS
      • http://dokuwiki.192.168.1.64 -> http://192.168.1.64:8080/

Caddy and DNSmasq are superfluous, if you’ve got a good memory or bookmarks, you don’t really need them.

VPN back into home is a lot more important. You definitely do not want to be forwarding ports to services you are running, because if you don’t know what you’re doing this could pose a network security risk.

Use the VPN as the entry point, as it’s secure. I also recommend running the VPN in a docker / podman container on an old laptop dedicated just to that, simply to keep it as isolated as you can.

Down the line you could also look into VLan If your router supports that.

I personally would not bother with SSL If you’re just going to be providing access to trusted users who already have access to your home network.

If you are looking to host things, just pay for a digital droplet for $7 a month, It’s much simpler, You still get to configure everything but you don’t expose your network to a security risk.

If you’re just going to VPN in to your home network, I’ve found caddy to be the simplest.