Repository navigation
Conversation
TimMonko
force-pushed
the
cf/06-deploy-cloudflare
branch
from
November 20, 2026 06:25
e50968f to
adad667
Compare
After each update, the workflow builds site/ and deploys it to Cloudflare with `wrangler deploy` on scheduled and manual runs, and as a preview version (pr-<number>) on pull requests from this repository; PRs from forks get no secrets and skip it. Pull requests also keep the built site as an artifact for review. GitHub Pages is no longer deployed: Cloudflare serves the same files. (npe2api's GitHub Pages mirror, https://napari.org/npe2api/, has no known users and stays with npe2api.) With Pages gone, nothing writes to this repository any more, so the job drops to read-only contents permission. id-token goes too: Google Cloud authenticates with a key file, not OIDC. A deploy uploads only the files whose content changed, so a run that updates a few plugins uploads a few files. worker/README.md covers local work, the one-time setup (an API token and two repository secrets) and the hostname switch-over. wrangler.jsonc enables the workers.dev URL and preview URLs, which is where the parity check runs before any DNS change. Ashley Anderson's cloudflare-poc branch first built this workflow shape: deploy on schedule, previews for PRs, and the update job feeding Cloudflare directly. Co-authored-by: Ashley Anderson <aganders3@gmail.com>
TimMonko
force-pushed
the
cf/06-deploy-cloudflare
branch
from
November 20, 2026 06:33
adad667 to
f4fce0d
Compare
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
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.
After each update, the workflow builds site/ and deploys it to
Cloudflare with
wrangler deployon scheduled and manual runs, and as apreview version (pr-) on pull requests from this repository;
PRs from forks get no secrets and skip it. Pull requests also keep the
built site as an artifact for review.
GitHub Pages is no longer deployed: Cloudflare serves the same files.
(npe2api's GitHub Pages mirror, https://napari.org/npe2api/, has no
known users and stays with npe2api.)
A deploy uploads only the files whose content changed, so a run that
updates a few plugins uploads a few files.
worker/README.md covers local work, the one-time setup (an API token and
two repository secrets) and the hostname switch-over. wrangler.jsonc
enables the workers.dev URL and preview URLs, which is where the parity
check runs before any DNS change.
Ashley Anderson's cloudflare-poc branch first built this workflow shape:
deploy on schedule, previews for PRs, and the update job feeding
Cloudflare directly.
Co-authored-by: Ashley Anderson aganders3@gmail.com
Stack created with GitHub Stacks CLI • Give Feedback 💬