Skip to content

Migrate Tatami website and future Sparkle feeds to Cloudflare Workers - #15

Merged
PangMo5 merged 2 commits into
mainfrom
pangmo5/cloudflare-hosting
Sep 14, 2026
Merged

PangMo5 merged 2 commits into
mainfrom
pangmo5/cloudflare-hosting

Conversation

@PangMo5

@PangMo5 PangMo5 commented Sep 14, 2026 •

Copy link
Copy Markdown
Owner

Deploy the existing website and signed release appcast to https://tatami.pangmo5.dev/ with Workers Static Assets. GitHub Actions retains the existing build and release flow, and the website artifact includes the release's signed appcast. New app builds use the subdomain directly through SUFeedURL.

Previously installed versions retain their old feed URL. The companion PangMo5.github.io migration supplies permanent redirects from pangmo5.dev/Tatami/... after the new product sites have been verified. Keep existing GitHub Pages compatibility endpoints during cutover.

Validation: Wrangler 4.131.2 dry run; local HTTP checks for the site's static files, appcast XML and cache headers, and 404 responses; actionlint workflow validation; Tuist generation and verification of the generated app Info.plist feed URL.
Tatami automation tests: 26 passed. Verified 35 generated documents and built 20 pages in 5 languages, including canonical subdomain URLs and query/fragment-preserving document links.

Root redirects: PangMo5/PangMo5.github.io#1

Deploy the website and signed release appcast with Workers Static Assets.
Use the product subdomain for website links and future Sparkle update checks.
Retain old installed-client URLs through redirects managed by the root website.
@PangMo5
PangMo5 merged commit 67396e6 into main Sep 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant