Giters

Yetangitu / Spodcast

Spodcast is a caching Spotify podcast to RSS proxy. Using Spodcast you can follow Spotify-hosted netcasts/podcasts using any player which supports RSS, thus enabling the use of older hardware which is not compatible with the Spotify (web) app.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Ready-made docker-compose file

dodekaphilist opened this issue · comments

commented

Since I already spent a couple of hours trying to get this running without success, I was wondering if it would be possible to provide a simple docker-compose file, that one could plug into Portainer and Spodcast would just work on a provided port. I imagine something like this:

version: '3'
services:
  spodcast:
    image: heywoodlh/spodcast 
    restart: always
    ports:
      - 80:80
    volumes:
      - ./spodcast:/data
    environment:
      SPOTIFY_USERNAME: "username"
      SPOTIFY_PASSWORD: "password"

By using environment variables, the initial setup could be improved so that the user would not be obliged to handle credential files himself but rather let the program do that.
Also at least for me, the whole web-server thing is really complicated with configuration and permission managment. I think, it would tremendously help beginners if something for this would be included in the docker image of Spodcast. After all, the application is of little use without a proper RSS feed server.

Since this might be a little bit more complicated to change, for the moment I would also just be happy to get some guidance how to setup a web-server in docker with the necessary steps for configuration. Thank you! :)

commented

Did you try the ready-made image from Docker hub as per the relevant section in the README? As to setting up a web server in Docker I think @heywoodlh has an example of such in his repo:

https://github.com/heywoodlh/dockerfiles/tree/master/spodcast-web

commented

Thanks for your answer.
I was able to set it up like described and it did download a podcast to my local drive. I found the experience more like using a command line than a docker container (at least those that I use regularly). I thought of a container that is constanly running and that's why I proposed the changes.

I wasn't able to setup nginx properly (even after lots of googling) which means I always got 404 at the specified port, and with php-apache it only did work partially after I renamed the index.php file (dot removed) to show the basic website, but I got permission problems (Forbidden) when navigating to the rss link.

Unfortunately, the files provided did not help me to figure out what I need to change...

commented

I'm currently working on getting Dockerfiles setup so that they will work with docker-compose. Should be in the next few hours I hope.

Once I get the docker-compose setup hopefully that will provide a more user-friendly setup.

commented

PR has been created: #18

commented

I can verify the docker-compose provided by @heywoodlh works great. Please note that you need to temporarily set the Cron docker to * * * * * at first, then set it back to 0 * * * * or whatever you prefer, the page will start out as a 404 until it actually downloads content for the first time. The docker-compose provided unadultered, creates 3 docker containers, one dedicated to PHP server, one dedicated to web page serving, and one dedicated for the cron scheduled tasks, and they do not shut off, they contnue running until manually shut off.

I have this running on my Unraid server.
image