You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub Actions is configured to publish this site once a day. Since the generation of the site is based on the RSS feed for the podcast host (libsyn), this means that new episodes are displayed within 24 hours of their publication.
libsyn does not have a hooks API, so there does not appear to be a way to more dynamically update the site when a show is published (without switching to a different host, which is tempting).
This has been working pretty well, but there has been a challenge. The source code for the website does not change often, and that causes the GitHub Action to timeout and stop running every day. The work-around has been to notice when this happens and then manually trigger the GitHub Action, which appears to get it unstuck.
An automated work around or solution needs to be developed to keep this from happening. Any ideas? This could probably be a simple as an IFTTT bot that monitors the RSS feed for changes and then triggers the GitHub Action.
This might qualify as a separate issue, but it'd also be nice to have some kind of alert set up to notice if the RSS feed was updated but the website was not.
I'm open to switching to a different podcast host, if there's one that has an "on-publish" web hook that we could use.
The text was updated successfully, but these errors were encountered:
GitHub Actions is configured to publish this site once a day. Since the generation of the site is based on the RSS feed for the podcast host (libsyn), this means that new episodes are displayed within 24 hours of their publication.
libsyn does not have a hooks API, so there does not appear to be a way to more dynamically update the site when a show is published (without switching to a different host, which is tempting).
This has been working pretty well, but there has been a challenge. The source code for the website does not change often, and that causes the GitHub Action to timeout and stop running every day. The work-around has been to notice when this happens and then manually trigger the GitHub Action, which appears to get it unstuck.
An automated work around or solution needs to be developed to keep this from happening. Any ideas? This could probably be a simple as an IFTTT bot that monitors the RSS feed for changes and then triggers the GitHub Action.
This might qualify as a separate issue, but it'd also be nice to have some kind of alert set up to notice if the RSS feed was updated but the website was not.
I'm open to switching to a different podcast host, if there's one that has an "on-publish" web hook that we could use.
The text was updated successfully, but these errors were encountered: