docker VS caddy-docker-proxy

FWIW, SWAG also allows you to open other services, like Wallabag (to replace Pocket), etc.

Wallabag, if you can get it running.

Wallabag - Pocket alternative, great Android and iOS clients, native MFA

I used the default config from the official GitHub page: https://github.com/wallabag/docker

I grabbed wallabag docker image, installed it, ran it accordingly ( the second SQLite command in the repo readme) .In browser wallabag asks me for registration with email and it'll complete sucessfully but the email never recieved, also the format of registration page(images, css, font style) is completely off. What am I missing?

It looks like there is already a github issue for making this multiarch. But you should be able to build the docker image yourself on your device. As long as you have git and docker installed on your raspi, run these commands:

Also found (this)[https://github.com/wallabag/docker/issues/71] which suggests that the images should be saved in /var/www/Wallabag/web/assets/images in the container, but that directory is empty as well.

git clone https://github.com/wallabag/docker.git

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