Workers Static Pages - Dashboard or Wrangler
Hello, I'm attempting to deploy a static site built with zola, and as this is a new project, as per recommendation in Pages docs I'm trying to use Workers instead of Pages.
I already have a repo on GitHub with the site, and I added a
I went to Cloudflare Dashboard > Compute > Workers & Pages > Create > Workers > Import a repository > Get started, connected to GitHub (org), and after I selected the repo the next step asked me for details of the project, but it said it will create a new Git repo for it. That was a bit confusing, but I went ahead to see what it would do, and it turned out it didn't actually create a new git repo, but used the one I had. However it also didn't seem to pick up any of the settings in my
So my question is, could you clarify what is the interaction between Cloudflare Dashboard and Wrangler? Is wrangler only used for integration with external CI/CD? Or can I use wrangler to create a project that uses Cloudflare CI/CD and git integration to automatically build the site on push?
I was looking for a way to configure this through code as much as possible. Would something like Pulumi or Terraform be better for this? (Although from brief look at them it doesn't seem like they can handle Cloudflare CI/CD configuration, nor static pages projects, and look to be more geared toward external CI/CD as well).
I already have a repo on GitHub with the site, and I added a
wrangler.toml with some basic configuration as per migration docs, so name, compatibility_date, routes (a single pattern with custom_domain = true), assets.directory = "./public/", and build.command set to install and run zola build (as per this issue).I went to Cloudflare Dashboard > Compute > Workers & Pages > Create > Workers > Import a repository > Get started, connected to GitHub (org), and after I selected the repo the next step asked me for details of the project, but it said it will create a new Git repo for it. That was a bit confusing, but I went ahead to see what it would do, and it turned out it didn't actually create a new git repo, but used the one I had. However it also didn't seem to pick up any of the settings in my
wrangler.toml as the domains and routes use the default workers.dev domain, etc.So my question is, could you clarify what is the interaction between Cloudflare Dashboard and Wrangler? Is wrangler only used for integration with external CI/CD? Or can I use wrangler to create a project that uses Cloudflare CI/CD and git integration to automatically build the site on push?
I was looking for a way to configure this through code as much as possible. Would something like Pulumi or Terraform be better for this? (Although from brief look at them it doesn't seem like they can handle Cloudflare CI/CD configuration, nor static pages projects, and look to be more geared toward external CI/CD as well).
Cloudflare Docs
Deploy your Pages project by connecting to your Git provider, uploading prebuilt assets directly to Pages with Direct Upload or using C3 from the command line.

Cloudflare Docs
A guide for migrating from Cloudflare Pages to Cloudflare Workers. Includes a compatibility matrix for comparing the features of Cloudflare Workers and Pages.

GitHub
Zola is no longer offered by default by the new build system and it is causing new user's sites to break. Would it be possible to make zola one of the preinstalled tools? I didn't see a pub...
