web-portal VS watchtower

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.

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!