Remove GitHub Actions workflow - #9
Open
bolu61 wants to merge 1 commit into
Open
Conversation
Deployment is pull-based: a cron job on the server polls main, builds, and syncs the output into the web root. No CI credentials or build step are needed on GitHub's side. See issue #7.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The site now deploys pull-based: a cron job on the server polls
main, builds withnpm ci --ignore-scripts && npm run build, and rsyncs_site/into the web root. No CI build or credentials are needed on GitHub's side, so the workflow is removed.Note: this also removes the build check — a commit that breaks the Eleventy build will surface only in the server's deploy log (
journalctl -t site-pull), not on the PR. Accepted trade-off for keeping the setup minimal.Part of resolving #7 (closed separately with the full context).