You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
.zip
)The text was updated successfully, but these errors were encountered: