web-portal VS gluetun

I am the creator of Web Portal which is a web dashboard. It has a plugin system and is written in python, so should be easy to expand.

github.com/enchant97/web-portal

Web-Portal is a web app written in Python using Quart, that aims to provide an easy and fast way to manage the links to all of your web services. It has been designed to run through docker and it is recommended to put it behind a proxy like Nginx for custom routing and domain names.

Web Portal Lite is a web dashboard to manage a page of links. It offers a minimal feature set to the feature rich Web Portal. Designed for users who just want to create a fancy looking links page and not worry about the advanced features. Unlike Web Portal which features a full ui editor, this "lite" version uses a basic yaml file for configuration.

Here's the repository link: github.com/enchant97/web-portal. Theres also a lite version, that's still in development.

Web Portal

Web Portal V2 is now released. It has been completely re-written, providing much more functionality, while still using minimal resources. Image and more below.

Before I release V2 I would like some testers (for feedback as well as bugs) As limited people have tested V2, I have made it easier to try it out. There is now a demo instance available at: webportal.demo.enchantedcode.co.uk. Docs and such are available on the 'next' branch at: github.com/enchant97/web-portal/tree/next. Thanks for your time.

If you want to test it out you will need to ensure you are on the 'next' branch and you will need to build the docker image yourself. Any documentation is now also located in the docs folder. You can access the repository from here: https://github.com/enchant97/web-portal/tree/next. Thanks for your time.

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