o

with cloudflare workers/functions or its embedded with cf pages?

Functions, which is part of Pages

Build Hooks for Page Deployments... It would be nice to have a hook (worker) we can call when a deployment is complete (pass/fail). That would be very helpful.

Exists - https://dash.cloudflare.com/?to=/:account/notifications

WHAAAAA!? I had no idea! Thanks!!

env vars per branch, i.e. if I want to put in a different API key or something into staging deployment vs production vs preview builds

Allow inline comments on redirects

/hello /world # a comment

gets flagged as invalid currently)

With the further unification of Workers and Pages as noted in today's CF blog posts, are there any thoughts to having some sort of unified config file for Pages — e.g.,

CFPAGES.TOML

or similar — that could be used as a locally saved alternative to the GUI? Might be handier for some devs who prefer local version control of such items and who also don't want to click around in the GUI. (I've heard some devs' comments to that effect.)

wrangler.json

probably

Does that address Pages, too, though?

Already being considered

Can you post this one to the workers-sdk repo please?

https://github.com/cloudflare/workers-sdk/issues/3255

Ty!

I would really LOVE it if I were able to configure the a pages project to have the "production branch" point to 1 git repository and the "preview branch" point to another repository. I have business reasons to keep them separate, and as of right now I have to create two separate pages projects to be able to accomplish the equivalent functionality.

You could use wrangler pages publish for this?

with

--project-name

and

--branch-name

I've not seen that requested in the whole time I've been here, so you're probably better of using that instead

In one of yesterday’s events here, there was a brief — and briefly contentious 😆 — mention of a possible config file for those who want to maintain local version control of their configs rather than switching back and forth around the GUI. The team made it really clear 🤣 that they’d rather not support YAML and would prefer JSON. Thus, here is a proposed example in JSONC (allowing comments, which is a desirable capability from a user standpoint, yet not invoking nasty red squiggly marks in VS Code). Hope it helps in some small way. cc: @User https://cdn.discordapp.com/attachments/920749372256419930/1108709198218412052/cfpages.jsonc

YAML ❤️

Yeah, I got the message yesterday. 😄

I have a web application that uses a large WASM file that is larger than the 25meg limit. It would be good if that limit could be increased.

The wasm file is less than 50 megs. This limit is preventing me from being able to move all my sites over to cloudflare pages.

You'd have to store it in R2 and link to it - Pages is unlikely to support files above 25 MiB in the near term.

Does anyone know if something like this is planned in the near future?

wildcard custom domain for cloudflare pages

No joke, exact same issue. I have a godot project and It's taking up too much for cloudflare pages to handle. Everything else is perfect, but this one thing is preventing me from going from netlify to this service. I please ask that, while not right now, the limit be raised even just slightly if possible.

Is there any feature for branch based environment variables rather than preview and production environments?

This is an architectural limit, not an artificial limit. The backing store of Pages (Cloudflare KV) actually has a max value size and as kian said it's unlikely to be raised in the near future, unfortunately.