Hey there - I'm the PM for Pages! Super excited about this release today. We also announced our support for GitLab and partnerships with several CMSes! Happy to answer any questions.
It's really exciting to see Cloudflare Pages keep progressing!
Any plan to eventually offer drop-in support for Next.js? (Not just static builds, but the backend server/serverless functions too, like Vercel... maybe mapping certain APIs to Workers?). It would be lovely to be able to leverage the power of that framework on Cloudflare infrastructure.
Edit: Next and frameworks like it solve the "I love the idea of serverless, but don't want to reinvent the whole backend from scratch" problem. It's nice to have a framework abstract away problems like routing, caching, invalidations, buildchains, image transformations, etc. Cloudflare Pages and Workers can do almost all the same things, but requires more coding and configuration... that's the only reason we went with Next + Vercel instead of Pages.
there is https://github.com/flareact/flareact in development by a shopify engineer, worth checking out... seems like a good architecture for deeper integration with workers runtime
Agree. Also, FWIW, what Cloudflare built is definitely a nice option. I would prefer even closer integration though and will be test driving this.
But… This is almost just like an index.html and api.php file on a server. I think what devs really need/want is the Svelte Kit adaptor but an official Cloudflare way.
Edit: Apparently the functions support parameterized files like .functions/friends/[name].js [1] which creates a lot closer integration. Put that feature front and center! I think this really solves many issues.
Thanks for bringing this up! It's definitely something that is on our radar. We're looking into improving the experience with frameworks, and Next is one of them!
Is there a way to push content directly to Pages instead of having it pull from Github or Gitlab? Many teams have their own deployment tooling with pre-existing git integrations, and would rather add a Pages target to that. For example Netlify lets you bypass their github pull feature. Does Cloudflare?
I'm interested in non-git deployment as well. For an image-heavy site, I would really prefer to avoid having to store static assets in GitHub so that I don't have to deal with git LFS. It would be nice if their CLI tool could support directly deploying a Pages application.
Right now, you can only create a project through GitHub/GitLab. However, being able to upload your pre-built assets directly to Pages is something we are working on now! Listen out for updates!
Does Pages now support multiple deployments from a single git repository? When I looked a while back it seemed like there was no way to host multiple domains on CF Pages from a monorepo. GH Pages has the same limitation, but Netlify does support monorepos.
I hope this doesn't come across too aggressively, but if merely clicking "refresh" doesn't do the trick (as suggested through a recommendation to clear cache/cookies) please investigate some cache-busting techniques!
Hi! Do you know if this release changes the ability to enable wildcard subdomain routing to Pages without requiring a >$200/mo Enterprise plan? Its a feature Netlify offer in their $19 "Pro" plan and is a roadblock for us to fully leverage Pages.
What is your story with Pages and Rust Workers? Will they get the benefits of automatic deployment or is it still required to use Wrangler and manually wire things together?
Where is information on gitlab support? I didn't see it linked in the post. Is this just the main gitlab service, or are any third party gitlab servers possible?
I'm building a svelte-kit based blogging framework called Svekyll with a hosting service called ExtraStatic. It all uses gitlab on the backend and I'm very curious if you could author on ExtraStatic and then publish into cloudflare. Right now I use the static adapter but I'm interested in seeing if the cloudflare adapter just works.
ExtraStatic is interesting because it allows you to publish without really knowing git. You can publish using just email, or you can use the creator tool or the Android app to publish into gitlab and then it builds automatically. Hosting on cloudflare would be awesome.
Unfortunately, it looks like this only works with gitlab.com. I don't think my GitLab instance will work as this blog post describes. It's still an incredibly cool offering and I am sure there is a way to do it with just vanilla CI inside my GitLab instance.
Great announcements today. Hoping you can share any expected progress on the long build times (chiefly initializing the build environment itself), which right now constitute the only real down-side of CFP IMHO.
If I just wanted to deploy a blog from github to Cloudflare pages, what would be the best way of doing that without writing javascript? Is there a way currently?
Absolutely possible! If you've just got a folder of static assets, you can connect it up to Pages, and enter that directory as the "build output directory".
Tried that, what I really like about Cloudflare is that it offers me more freedom than Github which basically forces you to use Jekyll if I'm not mistaken.
Any plan to eventually offer drop-in support for Next.js? (Not just static builds, but the backend server/serverless functions too, like Vercel... maybe mapping certain APIs to Workers?). It would be lovely to be able to leverage the power of that framework on Cloudflare infrastructure.
Edit: Next and frameworks like it solve the "I love the idea of serverless, but don't want to reinvent the whole backend from scratch" problem. It's nice to have a framework abstract away problems like routing, caching, invalidations, buildchains, image transformations, etc. Cloudflare Pages and Workers can do almost all the same things, but requires more coding and configuration... that's the only reason we went with Next + Vercel instead of Pages.