Castopod Server is an open-source hosting platform made for podcasters who want engage and interact with their audience. Please note that Castopod is still under heavy development: it may not be 100% stable and some features are still being developed.
I have the problem @ericg adresses in the post above. I upgraded to version
1.0.0-67~ynh1 and my public page for castopod is now displaying the “whoops hit a snag” page.
In the solution listed here:
Yassin Doghri’s answer requires a backup of the castopod instance (which I have made) and also a backup of the RSS file, and Database.
How do I find the RSS file and Database in order to back them up after I ssh into my server?
I looked under /etc/yunohost/apps & I can’t seem to find the correct location of the RSS file or Database. Can someone help point me in the right direction, please?
Hi, i m trying to set up an external drive as main storage for castopod.
I tried with mounting hdd to “/var/www/castopod/public/media” but didn’t works for me.
Hello, I’m running Castopod on Yunohost (podcast.domain.com) and enabled the REST API with basic auth credentials (restapi.enabled=true, etc.) in .env.
When my script or curl hits any endpoint like https://podcast.domain.com/api/v1/podcasts or /restapi/podcasts, it always returns HTTP 404 with the header x-sso-wat: You’ve just been SSOed.
It looks like the Yunohost SSO portal is intercepting the request and never passing it to Castopod, so basic auth doesn’t help.
How can I configure Yunohost’s Nginx so the Castopod REST API routes bypass SSO and are accessible to scripts?
Given Castopod just released a minor upgrade I took the opportunity to fix the API authorization problem.
The /podcasts endpoint should now be available at https://podcast.domain.com/api/v1/podcasts, keep in mind .env was overwritten during the upgrade so you need to re-enable the API.
Also, contrary to the docs you need to send Base64-encoded user:password portion of Basic auth, like so: Authorization: Basic dXNlcjpwYXNzd29yZA== (curl --user user:pass already does that)
Due to significant structural changes in the database, this version may require several manual actions to migrate from alpha 41 to 55 (see