web-portal VS caddy-docker-proxy

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.

Caddy via Caddy Docker Proxy (network).

https://github.com/lucaslorentz/caddy-docker-proxy

It handles the routing to multiple dockerized projects on one server, by scanning docker compose files for labels and automatically setting up the required caddy configuration.

My go to is always this instead:

https://github.com/lucaslorentz/caddy-docker-proxy

Single label to a docker container and with correct DNS you’ll have an automatically managed certificate right away.

I have had a great experience with using this: https://github.com/lucaslorentz/caddy-docker-proxy

It combines caddy with docker-compose labels, making it super easy to spin up new projects that can immediately be exposed.

If you want a slightly heavier but more robust solution, caddy-docker-proxy[0] is a plugin that listens to the Docker socket and automatically updates the Caddy configuration based on Docker labels you add to containers.

I.e. it makes Caddy act a bit more like Traefik. Most of the time, you'll just add the label `caddy.reverse_proxy={{upstreams http 8080}}` to your containers and the plugin will regenerate Caddy's configuration whenever the container is modified.

[0] https://github.com/lucaslorentz/caddy-docker-proxy

I disagree, Caddy works great in Docker. See https://caddyserver.com/docs/running#docker-compose, and CDP is a project that autoconfigures Caddy from labels https://github.com/lucaslorentz/caddy-docker-proxy. Regarding plugins, it's super simple to write a Dockerfile to add plugins, we ship a builder image variant that can be used to compile in any plugins you want.

````

This way, Caddy will buffer the request and give 30 seconds for your new service to get online when you're deploying a new version.

Ideally, during deployment of a new version the new version should go live and healthy before caddy starts using it (and kills the old container). I've looked at https://github.com/Wowu/docker-rollout and https://github.com/lucaslorentz/caddy-docker-proxy but haven't had time to prioritize it yet.

Docker labels support is available via a plugin https://github.com/lucaslorentz/caddy-docker-proxy

Or caddy-docker-proxy: https://github.com/lucaslorentz/caddy-docker-proxy