Skip to content
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

Convert project back to Cloudflare Workers (vs. Pages) #134

Open
benvinegar opened this issue Dec 20, 2024 · 0 comments
Open

Convert project back to Cloudflare Workers (vs. Pages) #134

benvinegar opened this issue Dec 20, 2024 · 0 comments

Comments

@benvinegar
Copy link
Owner

benvinegar commented Dec 20, 2024

In the fall, Cloudflare announced that Workers can now specify static files. It's currently in beta:

https://developers.cloudflare.com/workers/static-assets/

Being able to provide static files was the big impetus to switching to Cloudflare Pages. Now that that major benefit doesn't matter anymore, it makes sense to switch back to Workers, because:

  • Simpler installation (e.g. won't be prompted for the production branch name when creating a Pages project, which makes no sense when installing from a .zip)
  • Easier to deploy one-off branches to production for testing (Pages will only deploy a specified branch to production, a serious limitation)
  • Workers have more capabilities, like Cron Triggers, which could open up weekly reports
  • Workers have better observability
  • Pages haven't received any meaningful updates in the last major Cloudflare product launch so it doesn't look great for their future
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

No branches or pull requests

1 participant