[markelliot]

I’d love to see a version of this (or Netlify, Vercel, etc) that didn’t bundle CI with the preview and deploy steps so that I can pick my own CI and then effectively use the “CDN” as the highly qualified host of my static assets.

[btheory]

https://www.moovweb.com/

https://developer.moovweb.com/

We built this as a 'control plane' for everything above your backend APIs. You can bring your own CI/CD and get the same 'infinite staging' and other features that help bring Jamstack principles to large, dynamic websites.

[ianwalter]

Me too. I hate that Vercel and Netlify limit my build to using Node v12 because that is what Amazon supports. Node v14 is LTS now but still no telling when it will be a supported runtime. I refuse to live without optional chaining!

[eli]

Couldn't you build that with Cloudflare Workers relatively easily?

[tyingq]

Yes, you can...the feature people have been using, which existed before Cloudflare pages is "Workers Sites". https://developers.cloudflare.com/workers/platform/sites

[soooe2]

So, the difference here is that pages is free?

edit: This offering appears fairly similarly to the paid Workers Sites one. What changed that this is now free?

[tyingq]

Workers, also now has a free tier, with some usage limitations: https://developers.cloudflare.com/workers/platform/pricing

The "Workers Sites" works differently than "Cloudflare Pages", at least from the developers side. You're using their wrangler tool instead of passing a git repo to their CI/CD setup.

[kmf]

hey, dev advocate for workers here!

you can definitely do something similar with workers sites.

we recently added workers kv - the storage mechanism behind workers sites - to our free workers tier, so you can host your static sites on workers for free as well.

pages is an evolution of that with better tooling/dx for people who want to get a static site up on our network and want things like deploy previews and pre-configured github integration.

if you want to just have workers do the hosting and want to do all the CI stuff yourself, you can use something like wrangler-action[1] to simplify the process on github actions, or just install wrangler[2] (our CLI) as part of your CI workflow and do `wrangler publish` at the end.

i wrote our github action, so if you decide to go that route, happy to help debug or look over the project to make sure it'll do what you want - i'm @signalnerve on twitter, DMs are open :)

[1] https://github.com/cloudflare/wrangler-action

[2] https://github.com/cloudflare/wrangler

[markelliot]

Maybe? It’s more that I’d like to pay for the managed service of hosting my assets, registering branches for long lived access URLs, getting preview links, and promoting my site to its latest version.

Differently: why are Cloudflare and others interested in running my build?

[pushrax]

They probably see that most people don’t want to deal with setting up their own build, and want to make adoption as easy as possible.

Though they should definitely make it optional.

[no_wizard]

I think the target market here appreciates the one stop Solution given the big players here have always offered that.

I think alternative build integrations would be good though I do agree with that full stop. There should be a way to hook into the system from an outside pipeline to notify that a build is ready and able to be uploaded

I’d bet it will be an enterprise only feature first once though once it happens, we shall see