By running a `wrangler pages deploy`
By running a
wrangler pages deploy
VCould it be bugged? I added project via Cloudflare Dashboard, as GitHub repo. Now, when I run
wrangler pages deployDeployment complete! Take a peek over at https://1d363017.support-7d8.pages.dev. The domain is correct for the project. But deployment doesn't exist in Cloudflare Dashboard. And it has same old settings. It only displays deployments triggered via git.Vnvm, it does create deployments, but with different ids then printed on CLI
Vshould new settings from
wrangler.toml be visible in Dashboard? i.e. vars?Vmaybe it breaks because of vars like these:
Vcause deployment fails with
Error: Failed to publish your Function. Got error: invalid or missing json property for binding PROFILE_INFO
Vyep, this was the case, idk where I learned to write vars like that, but they brake the process
VProbably because I was reading: https://developers.cloudflare.com/pages/functions/bindings/#environment-variables
And then clicked on first link https://developers.cloudflare.com/workers/configuration/environment-variables/
And then clicked on first link https://developers.cloudflare.com/workers/configuration/environment-variables/
USince altering every nested dependency manually is not practical, what's the recommended approach to adapting all parts of your project that depend on Node.js's crypto to be redirected to use Cloudflare's compatible node:crypto APIs?
I'd really like to use Pages to host my Ethereum dapp but using any of the standard Ethereum dependencies looks challenging. Is Pages not really well suited for this usecase?
I'd really like to use Pages to host my Ethereum dapp but using any of the standard Ethereum dependencies looks challenging. Is Pages not really well suited for this usecase?
MQuick question: is it possible to restrict the pages.dev preview links?
CYou can throw them behind CF Access yea, there's an option for it under Pages Project -> Manage -> "Access policy"
II think by default this is just the preview branches. If you want to restrict the production version (if your using a custom domain) you need to add additional rules
Vhow can I host multiple pages?
CIt's any preview deployment yea/everything besides the current production, which is what he asked. If you want to restrict the pages.dev itself, you're best off using Bulk Redirects
IYou mean a website with multiple sub pages or multiple different websites?
Cis there something going on in cf? I tried pushing 3 times (next.js), and it's continues to build, for hours. I had one going for 5 hours, i canceled it and pushed again, and now this is is also going for 3 hour 25 minutes, and still going
TI just did a push with a Vitepress site and it worked like normal. Are you seeing any log messages?
CSometimes I see nothing, like this screenshot, sometimes I see it's stuck as "Creating an optimised build"
by the way, it's 18 hours+
by the way, it's 18 hours+
RDo pages support cron job functions?
CNo
R
CWith convergence it will be able to have the same triggers for both pages and workers.
Rwhats "convergence"?
CThe Cloudflare Blog
Today we’re excited to announce that over the next year we will be working to bring together the best traits and attributes you know and love from each product into one powerful platform!
Rwooo
Rassuming its not ready yet
Ror is there a way to create a converged project
HNot yet no
Rany eta ideas?
R(roughly)
Rthis was posted in May of 2023, about a year ago
IIt's a long-term project at Cloudflare, so don't expect it to be completed short-term.
IIt'll also probably be done incrementally, with things slowly converging rather than just one release (like how the Workers/Pages dashboard is now one)
II didn't say it was without fault 
BI created a new pages project without first linking a github account, and created a wrangler toml. Now I can't link it with a github account...? The option to configure it is completely missing
Band there's no documented
wrangler.toml options to do the link or anything, in case it's meant to be configured in code
HIf a Project is created without a Git connection, then it must be recreated to add said connection
BHuh... that's kind of weird
BReading this blog post makes you think that you could move all of that into wrangler.toml now, maybe except for the literal link https://blog.cloudflare.com/pages-workers-integrations-monorepos-nextjs-wrangler
...but the only real thing that's been moved into wrangler.toml is
...but the only real thing that's been moved into wrangler.toml is
pages_build_output_dir? That's the only difference?The Cloudflare Blog
Today, we’re launching four improvements to Pages that bring functionality previously restricted to Workers, with the goal of unifying the development experience between the two. Support for monorepos, wrangler.toml, new additions to Next.js support and database integrations!
IIt's not really a matter of moving it into wrangler.toml, it's just the fact that currently the internal architecture differentiates between Direct Upload projects and Git projects and you need to recreate to make the switch.
IYou can't switch types via the dashboard either without a full recreate.
BYeah, that makes sense, still just seems... half-baked I guess
BAlso things like:
When used in your Pages Functions projects, your wrangler.toml file is the source of truth. You will be able to see, but not edit, the same fields when you log into the Cloudflare dashboard.This just seems to not be true at all. Environment variables are still editable by me in the cloudflare dashboard, and ones I've configured in the wrangler.toml are not showing up
V- You can pull config from Dash to wrangler.toml by using:
wrangler pages download config - You can push wrangler.toml to Dash by either running
(uses your git branch for context, so if you are not on production branch, it wont push production variables) or by pushing your code to GitHub.wrangler pages deploy
2b. If your wrangler.toml is bad, the push will fail. In your case, you probably might have some missconfiguration in wrangler.toml, that's why it isn't updating.
BThe build works fine and the build runner is even picking up my variables from the wrangler.toml correctly, so I’m pretty sure it’s well-formed
VLast week I was in a situation, where build was using wrangler.toml, but Dash didn't update the settings. So... After successful build, worker failed to run project, because of bad var. And Dash settings were old.
Build probably loads
After I fixed my
Build probably loads
wrangler.toml differently? idkAfter I fixed my
wrangler.toml, Dash settings started updating too, together with build vars.Vso you shouldn't assume, that if your build manages to read some of config, that it actually managed to push it to Cloudflare. It's probably two different operations.
HWere you checking whether the config matched the deployment, or the project itself?
HThe
wrangler.toml should at least be applied to the deployment, even if it may not apply to the project