Miniflux VS caddy-docker-proxy

I see this all the time and while at the time I thought the same there's so many good alternatives these days, even better than back then. All the interesting and small websites I want to follow still have RSS feeds so I feel like we can move on.

The two I use for many years already are:

- https://miniflux.app (OS, Minimal, web interface and can be used with all clients that support Fever or Google Reader API)

- https://reederapp.com

And like with most multiplatform apps, it doesn't look native at all on iOS. I prefer my current combination of: https://netnewswire.com + https://miniflux.app

Both open source too.

Recommend checking out https://github.com/miniflux/v2

n.b. I haven't tested importing 600+ feeds!

I really like miniflux it's PWA is very nice

Miniflux

Any Miniflux fans may find this blog post useful for a faster way of generating new themes using GPT.

ive had pretty good luck finding feeds for stuff i want to subscribe to. there isn't always an explicit rss link but you'd be surprised how many blog platforms provide a /rss or /feed endpoint by default. the reader i use is pretty good at finding them if i just give it a link to the home page.

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

I am trying now for some Days to use a Caddyfile additionaly to the auto generated files from lucas lorentzes caddy repositroy. https://github.com/lucaslorentz/caddy-docker-proxy