-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add port/fork for Cloudflare Pages #2
Comments
+1 |
Deployment guides (for a/o Cloudflare Pages) are in the making (including official Hyas plugins if applicable + example repos) |
Exciting, thanks for the update! |
Awesome, Waiting for the update. |
Here's the guide: Deploy your Hyas Site to Cloudflare Pages If you have any additions or improvements, let me know |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
---EDIT---
moving to Discussions section
---EDIT---
Summary
Would be great to see this great project ported/forked over to support Cloudflare Pages (in addition to Netifly), with similar features such as
_headers
and_redirects
and_functions
and the new/functions/
folder and supported functions within. Support for preview environments, environment variables are all available, so it seems a feasible port that would be beneficial for us deeply invested in Cloudflare and wish to use this platform. I'm not that familiar with modifying the npm build process to ensure that Cloudflare's build process properly generate the correct files and ensure they fall into correct folders in the right format and so forth.General documentation for Pages:
https://developers.cloudflare.com/pages/platform/
Existing migration guide from Netifly to Cloudflare Pages that might be useful:
https://developers.cloudflare.com/pages/migrations/migrating-from-netlify/
The text was updated successfully, but these errors were encountered: