🚀 Castopod v1.15 is out: giving some love to FrankenPHP on Docker!
Rebuilt the all-in-one Docker image on FrankenPHP + Caddy (replacing discontinued Nginx Unit).
Enjoy faster loads + lower latency with:
✅ HTTP/3 support
✅ HTTP range requests (audio seeking works perfectly!)
⚠️ Breaking changes for Docker users, see release notes: https://code.castopod.org/adaures/castopod/-/releases/v1.15.0
@Castopod
My instance went down after update to 1.15.0 tag. Background tasks were executing, but HTTP wasn't working. I rolled the image back.
Is it safe to update again already?
@yassinedoghri @Castopod
So Castopod isn't using SemVer?
@yassinedoghri @Castopod
But if backward compatibility breaks only for part of the users depending on configuration, it's still BC break 🤔
Docker image versions use the same versioning, so users like me may expect compatibility across all minor bumps.
I mean I understand that something annoying was fixed, but I for example got a notification from Google that they can't retrieve my RSS feed for example. That's kind of major problem too.
Still, thanks for pointing out to the fix.
@yassinedoghri @Castopod
Yeah, I've updated my Compose configuration and after that update was successful. Thanks.
@Castopod It's time to get serious and implement automatic updates for Castopod. It's 2026, not 1999... having to delete things and re-upload them via FTP is ridiculous.
@Steizam
Using Docker for your installation could help.
Here's not the best, but simple way to do this:
Run Castopod stack
Use a tool like Watchtower to pull new images by the tag you've chosen and automatically rebuild your containers when new image is being pushed.
By the way, @Castopod, it'd be nice to have a tag like 1 which follows all updates under 1.x.x, but wouldn't include 2.x.x versions when Castopod 2 comes out to avoid unexpected problems.
@skobkin @Castopod What they need to do is implement a system like WordPress has... where when there's a new version, the notification appears directly in the panel, and if you want to update, you simply click to download and overwrite (or delete what's no longer needed and copy the new version). I appreciate your suggestion, Alexey, but I'd prefer that they be the ones working on improving their tool.
system like WordPress has.
Yes, I understand that. Both as a PHP developer and Wordpress user.
I'm just proposing a solution for you personally.
I'd prefer that they be the ones working on improving their tool
Castopod has a bunch of end-user facing UX problems so this feature may be not a highest priority. At least it wouldn't be for me if I was developing it.
I suppose we're as a community are always welcome to contribute to what we're personally interested in.
Although if I'd personally found time to contribute, it'd be something like implementing clickable chapters or something like that, that listeners of my podcast are struggling with.
Especially considering that solution already exists for containerized deployments which I can guess should be far more popular these days than "drop files into Apache" ones.
@Castopod do you reckon we could skip this release if we don't deploy castopod using docker?
@Poslovitch @Castopod Yes, no need to upgrade for non docker users 👍
@Castopod Thanks! great news! Lot of people waiting for this change to have Range Byte Request working with the all-in-one image.
Amazing work.
CC @PapaFriki Lo mismo te interesa probar esto sin el parche que hiciste:
https://code.castopod.org/adaures/castopod/-/releases/v1.15.0
📔 We've also updated the Docker docs: https://docs.castopod.org/main/en/getting-started/docker/