Produce static site on GitHub and upload as artifact #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
robsimmons
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Taking advantage of #12 means that we need to have Twelf around while the wiki is being statically site generated, but it seems like the build infrastructure for static sites on render.com doesn't have the easy ability to install extra dependencies, as would be necessary to compile Twelf.
One can imagine several possible ways forward, the most tempting being using the inherent portability of WASM and the fact that we have a WASM twelf running around. But we also have Twelf compiling successfully with github workflows... so I'm going to take the approach of just moving the static site generation step to GitHub actions, and have the render.com process doing nothing more than polling GitHub for the right artifact.