Luke

A so-called “neutral accent” is still an accent.

You have a lot going on there all at once that could be contributing to the whole thing failing.

If it were me, I would try to get caddy working independently of everything else first, since it was your original problem, then layer in the other containers one by one in case you’ve got configuration problems in them too.

Caddy by itself is super easy to verify with something like a browse directive pointed at an empty directory.

Then add your tailscale container and configs, and check that you can still access the browse page from caddy.

Then add your Jellyfin container and adjust the Caddyfile to proxy to it.

Damn, that’s unfortunate, but good to know. Thanks for the info.

This seems like a really nice tool, congrats!

Too bad there is so much focus on AI though. The UI looks nice, and templating and being able to schedule posts would be super handy, but I don’t need an AI to write things for me. I find that using AI is ethically icky anyhow; I’d rather not have it in any of the tools I use.

Is it possible to disable all the AI features when using Postiz? Like, a boolean setting in the deployment configs would be great.

People need to stop posting content to YouTube. Quit giving them new leverage.

Even the linked article whines about how they don’t want to use Peertube because “the audience for the content is 100x smaller” but that’s at least partly a self fulfilling situation. Of course they aren’t going to have a large audience on Peertube when they don’t post anything there. Mirror your old content there. Upload new content there instead. Advertise your Peertube channel instead of YouTube.

There’s not going to magically be a huge audience out of nowhere on alternative platforms, it takes content creators to migrate first.

I am one of those people!

That’s working as intended; as the compose docs state, the command passed by run overrides the command defined in the service configuration, so it wouldn’t normally be possible to actually shut down all the containers and then use docker compose run to interact with one of them. Run doesn’t start anything up in the container other than the command you pass to it.

I’m not familiar with funkwhale, but they probably meant either to (a) shut down all the containers except postgres so that running pg_dump has something to connect to, or (b) use exec as you have done.

Personally, I do what you did, and use exec most of the time to do database dumps. AFAIK, postgres doesn’t require that all other connections to it are closed before using pg_dump. It begins a transaction at the time you run it, so it’s not interfering with anything else going on while it produces output (see relevant SO answer here). You could probably just leave your entire funkwhale stack up when you use docker compose exec to run pg_dump.