-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[DOCS] Update Cloudflare Pages Deployment Guide for Big-AGI 2 Compatibility #739
Comments
@saliksik pull requests welcome. |
I was able to get it deployed to cloudflare by setting the NODE_VERSION environment variable in the page settings to be 22.14.0 as the only step missing, however I am now seeing an issue at runtime with calling the listCapabilities endpoint. Cloudflare throws an error stating: |
Cloudflare is a great platform, and I'm considering making it the preferred cloud platform in the future, due to great edge support, egress pricing, edge DBs, etc. Background: the Big AGI code is mostly a client-first React application with a (very weak, by design) dependency on NextJS, for client side routing and bundling, mostly. The server side has mostly (or maybe exclusively) a tRPC server, which could be decoupled in the future. However right now a cloud runtime (Cloudflare) needs to support both: 1. NodeJS vercel runtime, and 2. NextJS Edge runtime (may fall back to 1) -- without any code changes. I welcome anyone looking seriously into this topic (with the objective of producing a more agnostic Big-AGI that would run on any platform). The following are promising:
I make my time available to someone that's good with Cloudflare and NextJS apps on Cloudflare - just reach out anytime (not a huge priority for me at the moment, given the volume of things going on). |
The current Cloudflare Pages guide for Next.js no longer works for deploying Big-AGI 2.
The text was updated successfully, but these errors were encountered: