-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New guide for migrating from Vercel to Workers #21959
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
New guide for migrating from Vercel to Workers #21959
Conversation
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryAdded a new tutorial for migrating applications from Vercel to Cloudflare Workers, providing detailed steps and configuration guidance.
Added Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
|
||
## Frameworks | ||
|
||
Some frameworks like Next.js, Astro with on demand rendering, and others have specific guides for migrating to Cloudflare Workers; refer to our [framework guides](/workers/frameworks/) for more information. If your framework has a **Deploy an existing project on Workers** guide, follow that guide for specific instructions. Otherwise, continue with the steps below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!!! This is exactly what took me like 20 minutes to wrap my brain around before.
src/content/docs/workers/static-assets/migrations/vercel-to-workers.mdx
Outdated
Show resolved
Hide resolved
…rkers.mdx Co-authored-by: ToriLindsay <[email protected]>
Co-authored-by: ToriLindsay <[email protected]>
…s-desmond/cloudflare-docs into tdesmond-vercel-to-workers
Congratulations @thomas-desmond, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cma44uc7122870cjrxcat6yzn This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
* New guide for migrating from Vercel to Workers * Create migrations folder under static-assets and move related content into folder * Update src/content/docs/workers/static-assets/migrations/vercel-to-workers.mdx Co-authored-by: ToriLindsay <[email protected]> * Update src/content/docs/workers/static-assets/migrations/index.mdx Co-authored-by: ToriLindsay <[email protected]> * Fix broken links --------- Co-authored-by: ToriLindsay <[email protected]>
Summary
This adds a new tutorial for migrating from Vercel to Cloudflare Workers. Heavily based on previous article of migrating Vercel to Pages. https://developers.cloudflare.com/pages/migrations/migrating-from-vercel/
Documentation checklist