News for hackers. Stuff that matters.

A comment on Migrating from Netlify to Cloudflare Workers Sites for 2x Performance (2020). Parent comment

Re:Migrating from Netlify to Cloudflare Workers Sites for 2x... by PinkPigeon on Friday February 11, 2022 @07:28AM (#30300620)
Pages doesn't allow for direct deployments. Has to go via git repo + webhooks. We make static sites with our CMS and don't really want to integrate another thing into our workflow. Lots of CF and git API calls to automate the whole thing reliably. Thus, we're sticking with workers sites for now. Pages is an attractive offering, however.
[ Parent | on HN ]
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x... by barake on Friday February 11, 2022 @08:51AM (#30301444)
Yeah, the totally managed deployment for Pages is great to get started, but not being able to run through our regular CI tool is a major bummer and has us also sticking with Worker sites.
[ Parent | on HN ]
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x... by nagisa on Friday February 11, 2022 @09:06AM (#30301618)
It is possible to use the CI to build the website. My static site generator is written in haskell, so for me CI was the only option. Here's how (GHA is my CI):

* build the website and produce a GHA artifact packaged as a zip or somesuch;

* invoke Pages deploy hook API endpoint;

* within cloudflare pages run a (e.g. python) script to download the artifact, decompress it and place the resulting files in the correct output directory.

Ideally these kinds of gymnastics wouldn't be necessary and it would be possible to just run something like `cfpages deploy .` but it is not absolutely impossible to get something working, either.

[ Parent | on HN ]