#Dynamic website examples github for free#
#Dynamic website examples github install#
#Dynamic website examples github update#

Reflecting updates requires cache-busting.

The maximum size of a payload you can send to the /dispatches endpoint is limited by GitHub to ~70kb. The action can often take 5-10 seconds to kick off, then depending on what your action does it may take 30 seconds to run, then another 10-30 seconds for GitHub Pages to reflect the repo changes. GitHub Pages and GitHub Actions weren't exactly designed with this use-case in mind, as such there are some limitations you'll run into: Make sure the commit and push step handles rebasing to allow for concurrent runs and add some retry steps in case the rebase push fails.Д«ody: JSON.stringify()ДЇor those of you that prefer technically incorrect but kind of legible diagrams, this is what is happening behind the scenes: Limitations

#Dynamic website examples github update#

Create a GitHub action in the same repo that accepts a repository_dispatch trigger (triggered by the fetch call), modify some data, commit it back to the repository that will update the GitHub Pages site.

Add a fetch call (like below) as part of some user action on the GitHub Pages site itself.

#Dynamic website examples github install#

Install the GitHub app to your repo to allow repository_dispatch to be called unauthenticated.

If you want to spin up your own version of the app/function, source is available here. This allows you to delegate permission for action runs on a specific repo to the GitHub app, and then make API calls to it's public-facing Azure function endpoint to trigger a repository_dispatch event. I've created a GitHub app to support this flow, including the Azure function necessary to proxy the requests to GitHub. So until GitHub add tighter scoping controls (ideally a specific repo and only permission to run actions) we have to use the other option, a GitHub App. You can create a PAT (Personal Access Token) and use that, however if you were to publish that on your GitHub Pages site it would give any visitor the ability to modify all of your repos on GitHub.

Triggering an action with repository_dispatch requires you to pass a bearer token. There is however one barrier to this approach, authentication. The repo update updates the GitHub authentication.That action run then updates the repo and.Makes a HTTP call to trigger an action run.It's not hard to imagine when combining these two features of GitHub that you could make a flow of data such that your GitHub Pages website:

#Dynamic website examples github for free#

On GitHub, you can also convert your repository into a full-blown static website for free using GitHub Pages. You can trigger an action run by one of many ways, but in this post we'll focus on repository_dispatch, which allows you to trigger an action from a HTTP request to a GitHub API endpoint. GitHub allows you to create actions in your repository, these are basically CI flows that can (among other things) make changes to files and commit them back to the repository.

Integrated this solution into my earnings tracker website, where you can submit other companies to be added to the earnings lists without any sign in.

If you're someone who wants to cut to the chase and see what can be built, I made: Best of all, this works with just a free GitHub account! But what if the contents didn't have to be completely static? In this post I'll outline how you can make a dynamic website powered by GitHub Pages and GitHub Actions and explain the nuts and bolts of how it works. GitHub Pages is one of the most popular tools for developers when it comes to static site hosting.