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

Cloudflare compatibility(search,redirect,404) #154

Closed

Conversation

coatsandhats
Copy link

Resolves #153
-Wrangler.toml to allow module syntax in page functions -404 changes to allow cloudflare auto 404 recognition -Functions/search.js for search functionality
-_redirects for user specified redirection
-.node-version for specifiying the node version for cloudflare builds -.elventy.js changes to passthrough _redirects

-Wrangler.toml to allow module syntax in page functions
-404 changes to allow cloudflare auto 404 recognition
-Functions/search.js for search functionality
-_redirects for user specified redirection
-.node-version for specifiying the node version for cloudflare builds
-.elventy.js changes to passthrough _redirects
@oleeskild
Copy link
Owner

After the recent upgrade to the search functionality, a serverless function for search is no longer needed. Everything is handled on the client side. Also the 404 pages are resolved at build time, so there is no need for an explicit redirect anymore.

But I'd be happy to accept a PR for the wrangler.toml file and .node-version. If it's possible, it would also be great if you could explicitly add the build command to the wrangler file as well. (Similar to the netlify.toml file)

@oleeskild oleeskild closed this May 3, 2024
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.

No cloudflare pages compatibility
2 participants