Open yattoz opened 2 years ago
Hello,
Concerning the CORS, it is not used in production, see production configuration. It was used only when developping locally, to bypass cors issues.
As I don't have the hand on all the pipeline, I just send an artefact with the correct option to Amo.
Concerning your issue, I have no idea. I would need more information, if it happen again, could you give a look at the network and check what is happening. Usually, when the next song timer arrives a 0, it should fire a call to retrieve the next schedule. And until, we don't retrieve a new schedule, we retry.
I think that the next song timer is broken, it should display the time until next song, but it displays zero.
As seen in this file
https://github.com/Lukinoh/radio-tsumugi/blob/master/public/config.json
I noticed that you used the API returned from from https://tsumugi.forum-thalie.fr/get_api_result.php (I don't really understand why you used a CORS-enabled proxy for it, since it's the same domain as the website.) Also, it seems like the response from here is not pure straight JSON, it's wrapped in parentheses, it's a bit less practical.
If you can use a CORS-enabled proxy, why not use the original API from the Airtime server? It's https://radio.mahoro-net.org/airtime/api/live-info-v2