Hey, I’m on Cloudflare’s Developer Advocacy team — this is a top priority for the Pages team right now and big improvements to the build time are being actively worked on!
Wow, this looks so awesome! Really simple UI too — gonna have to give this a try. I was just struggling with some client-side image upload stuff last week, and I love the idea of doing the full service integration from client to backend as a product.
BTW - I’m part of the dev advocate team at Cloudflare, would you want to chat sometime about your experience with Images? Definitely would love to hear your perspective as a dev on what could be better!
Pages has actually been GA since April of this year[1] - since then, we've released support for deploy hooks, redirect/custom header files, GitLab support, and as you mentioned above, a Workers function integration.
We have a really excellent team building Pages, and we still think there's a lot of unexplored territory around Pages/Jamstack and how it interacts with serverless and edge functions. Exciting times!
The story around types in Workers should be leaps-and-bounds better than it was a few months ago (thanks to the work outlined in this blog post) - would love to hear your thoughts on this new work, and hope it helps!
Quick plug I'll drop in here (I manage Cloudflare's Developer Advocacy team) - in addition to Durable Objects reaching GA, we also released a great open-source codebase today to help scale your Durable Objects-based projects.
It has built-in sharding and communication between connections/shards - basically how we would recommend people build with DO if they want to hit the ground running.
Trying for like an hour to set it up, but it keeps failing on cloning repository. That is definitely not a good first impression, specially because the message doesn't say anything, just 'internal error', so it's impossible to debug and try to fix.
Googling for the error, I found a few similar questions, but all were responded with: go to discord. So... there's absolutely no way to sort it out by myself or without using discord?
```
20:54:21.533 Initializing build environment. This may take up to a few minutes to complete
20:54:56.056 Success: Finished initializing build environment
20:54:56.056 Cloning repository...
20:54:59.840 Failed: an internal error occurred
```
I have a lot problems with builds with this "internal error" too.
I have 2 websites, both gatsby
I tried both:
1) gatsby build
2) fully static files (gatsby build on my local computer) and only public dir added to github repo
Websites 10.000 files and 13.000 files
(small files 1kB to 300kB) html, css, js, png and webp
Sometimes my build is succefull for this 10.000 files website - like 1 of 5 tries
But most build tries fail when deploying:
06:58:47.583 Finished
06:58:48.061 Deploying your site to Cloudflare's global network...
07:18:07.790 Failed due to an internal error
It was my understanding that I had to upgrade each domain to "pro" with $20/month (say, if I wanted pro features like web-analytics on each). Is that not the case?
On netlify.com, "pro" is $19/month per account (not per domain).
hi there! cloudflare pages pm here :)
we certainly plan to (nothing against gitlab!!), likely in the next couple months. my email is rita at cloudflare. happy to keep you posted
hey, kristian from the workers team here - i wrote these docs, so this is good feedback :)
we don't have any plans to get rid of workers sites! but we do think that for most people deploying static sites, pages is a better fit than workers sites.
when we do talk about the future of pages versus workers sites, we're generally talking about making it easier to deploy serverless functions /with/ your pages sites - providing better tooling and DX around that is a super high priority for us.
the interplay between workers serverless functions and static asset serving via workers sites is still a really strong use case (and IMO a thing that workers is uniquely capable of doing) that we don't have any plans to shelf. again, i wrote the docs here so this is on me if it came across as "we're getting rid of workers sites" - i'll take a shot at improving these docs and helping clarify that next week!
Haven’t uploaded for a bit but just set up the new studio and hoping to begin again in the next month or so.