Magnetico VS gluetun

This is really neat. I'll need to check it out. A couple years ago I ran my own instance of Magnetico (https://github.com/boramalper/magnetico), but this project looks a lot more polished.

This is likely your best bet, but I'd recommend you use postgres over sqlite, this is however where development died so some features like search or stats aren't implemented while using pg as the db.

You can create decentralized bittorrent indexers though (see https://github.com/boramalper/magnetico as an example)! This means you can search for bittorrent files without having to rely on a centralized service (although building the index does require some time & storage space of course).

https://github.com/boramalper/magnetico

Someone else did this a while back, universe continues to exist.

I just get a rickroll gif on your link. Did you mean this project?

"Autonomous (self-hosted) BitTorrent DHT search engine suite."

https://github.com/boramalper/magnetico

Although I admit, that I would love to see a maintained DHT search solution (like magnetico or dhtcrawler2).

Yeah, you probably found it. Abandoned, yes, but not necessarily unfinished.

A magnet search is easy enough to self-host, I can provide you with instructions to self-host a clearnet magnet search engine over I2P in the meantime, but you can probably figure it out from this: https://github.com/boramalper/magnetico which is an easy to self-host DHT search engine.

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki