5 ms·

Why use Cloudflare Workers for a Hugo site when they have Pages[1] that is specifically designed for static site build tools like Hugo, Jekyll, etc? [1] https:

Why use Cloudflare Workers for a Hugo site when they have Pages[1] that is specifically designed for static site build tools like Hugo, Jekyll, etc? [1] https://developers.cloudflare.com/pages/framework-guides/deploy-a-hugo-site https://developers.cloudflare.com/pages/framework-guides/dep...

rmbyrro 5y ago
Seems CloudFlare is really becoming a jack of all trades, which is cool because they are more and more a [developer friendly] replacement for those big cloud providers.
- BeefWellington 5y ago
  > more and more a [developer friendly] replacement for those big cloud providers. They ARE a big cloud provider.
  - rmbyrro 5y ago
    Yeah they certainly are. But their services catalog only recently started to approach the: "hell, I can pull an entire commercial app just out of Cloudflare infra". There are still a few missing spots, but seems they'll close the gaps pretty soon. Excited to see.
PinkPigeon 5y ago
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.
- barake 5y ago
  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.
  - nagisa 5y ago
    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.
kenrose 5y ago
This post was written in 2020 before Cloudflare Pages was launched. Presumably Pages was created because they saw a lot of people using Workers and KV for this use case.
- bastawhiz 5y ago
  Exactly: if the author had waited another four months, they would have been able to save themselves a lot of trouble.
abiro 5y ago
Does CF Pages support atomic deployments yet?
pwdisswordfish9 5y ago
Cloudflare Pages is hardcoded to GitHub (rather than just Git).
- tibyat 5y ago

rmbyrro 5y ago

Seems CloudFlare is really becoming a jack of all trades, which is cool because they are more and more a [developer friendly] replacement for those big cloud providers.

BeefWellington 5y ago
> more and more a [developer friendly] replacement for those big cloud providers. They ARE a big cloud provider.
- rmbyrro 5y ago
  Yeah they certainly are. But their services catalog only recently started to approach the: "hell, I can pull an entire commercial app just out of Cloudflare infra". There are still a few missing spots, but seems they'll close the gaps pretty soon. Excited to see.

PinkPigeon 5y ago

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.

barake 5y ago
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.
- nagisa 5y ago
  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.

kenrose 5y ago

This post was written in 2020 before Cloudflare Pages was launched. Presumably Pages was created because they saw a lot of people using Workers and KV for this use case.

bastawhiz 5y ago
Exactly: if the author had waited another four months, they would have been able to save themselves a lot of trouble.

abiro 5y ago

Does CF Pages support atomic deployments yet?

pwdisswordfish9 5y ago

Cloudflare Pages is hardcoded to GitHub (rather than just Git).

tibyat 5y ago