@skobkin @Castopod Check the release notes, you'll need to tweak your compose file.

Let me know if you're still having trouble.

@yassinedoghri @Castopod
So Castopod isn't using SemVer?

@skobkin @Castopod
It is, but I've broken the rule exceptionally because v1 users using Docker were having annoying issues with HTTP range / audio seeking because of the old Nginx Unit base image.

Non docker users can upgrade with no problem.

@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.

@gubi @Castopod
That's exactly that, you won't loose any data upgrading.
You may just change the internal mappings as written in the release notes and you'll be good to go 👍

@yassinedoghri @Castopod Hi Yassine, I was searching a docker compose template for Castopod 1.15.x and I found this template in the official castopod documentation:

https://docs.castopod.org/main/en/getting-started/docker/

Nevertheless in this yml template the port mapping is still

- "8080:8080" for HTTP

and not

- 8000:8080 as suggested here in the release notes:

https://code.castopod.org/adaures/castopod/-/releases/v1.15.0

May I assume that the full template could work with v1.15.4 changing

- "8080:8080"

in

- "8000:8080"

or should I change sthing else?

@gubi @Castopod

Yes! If you take the template and change the mapping to "8000:8080", it'll work.
No need to change anything else other than the environment variable values of course.

You could also keep the mapping as "8080:8080" and instead edit your reverse proxy config from localhost:8000 to localhost:8080 (as written in the docs)