milaq
commented
4 years ago Hey Fred,
thanks for your ideas. Station reloading sounds solid. I'll make it so that the custom station configuration will be reloaded when directly accessing them.
In the longer term, we will change the format for storing custom stations. We want the stations to be editable by some kind of web UI maybe. I can imagine that we are using JSON or even an SQLite db for that matter. At least we will change the YAML structure a bit.
I find your idea with the podcasts interesting. It is definately doable but we need to get a solid base set up first. I'd like to postpone this a bit until we have 'full' base functionality and most of the open issues are resolved.
I'll tag this as enhancement and keep it open. If you have any more ideas or thoughts regarding this feel free to contact me or write it into this issue.
Cheers
Hi milaq,
For your information, I would like to modify my stations.yml file from another machine without stopping the daemon. To do so I've simply added: "my_stations.set_config(None)" in "landing" function. So I can edit the file from a desktop computer, let YCast running on another (server) computer, and on the HTR simply going to the top menu, the file is reloaded.
My plan also is to include automatically some podcasts from RSS feeds, and to write them in my stations.yml file. I've already tested that podcasts I usually download work properly as stations in the .yml file (so, without the need to download them on a server, and without the need of a DLNA player application => this is really better than what I had with vTuner). What I would like is to automate completely the process.
Do you think it could be an interesting feature to add ? (station.yml or another config file would contain RSS links and automatically include them in the menu)
Thanks,
Alfred.