-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration to GitHub pages #103
Comments
This seems perfectly reasonable! In fact, the website itself already works on GitHub Pages, because it's just a basic Jekyll website. There's already a The only downside is that the website will build and update less fast. This is actually one of the main reasons we moved away from GitHub Pages (except for emergencies) — because it was quite slow to update. Their caching is crazy aggressive. (It's your decision — maybe they've improved or maybe it's still worth it anyway.) It's just the other services that break when we point the domain to GitHub Pages. You can view the
|
So some first attempts at making sure this can go smoothly
|
Nice!
Oh that's a very good point — we don't need to ask Informatics to update the CoSign redirect URL, because you can just redirect Cloudflare side! Nice find. One problem (unrelated to Cloudflare redirection, but related to CoSign) is that certain cookies will probably now only be set for the Two possible solutions for that:
|
I got every so slightly sidetracked by #23 😂, and I think the outcome of that will decide the outcome of this, so I'm closing this for now |
Since this is a fairly static site, I'm thinking that it could be hosted on GitHub pages, building on push with a GitHub action. The Co-sign stuff needs to be hosted on Tardis, of course, but the site itself should be fine on Pages, I think? This would reduce the number of services that need to be managed, and simplify the setup. Unless there are any issues with this that I haven't thought of (cc @qaisjp), I can take a stab at this tonight.
The text was updated successfully, but these errors were encountered: