does the project root directory refer to the folder that contains appsettings.json?
does the project root directory refer to the folder that contains appsettings.json?
Iappsettings.json is a framework-specific file. But assuming that your site is built from that directory (i.e to build your site you enter that directory and run some command) then yes, that's the root directory.
IRoot directory = where you run commands to build your site
Build directory = the directory where build outputs are placed (i.e. the final HTML/CSS/JS that is deployed)
Build directory = the directory where build outputs are placed (i.e. the final HTML/CSS/JS that is deployed)
Mand im also assuming that when i point the build directory, pages is able to pick up index.cshtml....
II don't believe Pages supports cshtml.
II'm assuming cshtml here needs to be rendered by a C# server like ASP.NET which Pages won't (and can't) do for you
IIf it's a C# based site you need to build to static HTML only, no C# in the output.
Mdo you have any recommendations on how i can deploy a website that is built on c#?
IYou'll need to completely build it to a static site to deploy to Pages. That means you can't run any C# code for any reason other than at build-time. If you want to deploy a C# site that runs C# at request-time you should look at alternative options like Railway or Fly.io for a managed platform, or a standard VM at a place like Vultr or Hetzner if you want to manage things yourself.
AHello, my api seems in under ddos attack, domain migrated in cloudlfare, please let me know how to fix this
FPlease do not post your question in multiple channels per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
Kdoes something wrong with cloudflare pages?
I got this error when redeploying today... i didn't change
I got this error when redeploying today... i didn't change
toml file at all, yesterday i depoyed normally
E?pages-deployment-id
FThe Pages deployment ID is a unique build identifier.
It's the UUID in the browser bar (for example, a URL would be
This ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.
It's the UUID in the browser bar (for example, a URL would be
dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID where the deployment ID looks something like a398d794-7322-4c97-96d9-40b5140a8d9b).This ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.
ECan you share the deployment ID for this?
GSeeing the same issue when I retry a previously successful deployment
ECan you share the deployment ID for this?
G337c62c4-037d-4e6f-8538-0cc599c2deb3
EThank you
SHey, does pages functions have any profiler? I'm trying to check where the most time is spent so I can reduce our API's response times
WHey, the release has been rolled back. Can you do a new build and confirm it works now?
WSame with you, could you please retry now?
EAlso @Kiecooboi@george_webb I'd liike to confirm, is there a
wrangler.tomlAnd also if so, is there a
pages_build_output_dir or similar param added?
GDeployment retried and now successful after the roll back
WAwesome, did you have a wrangler.toml
If so, recently added?
If so, recently added?
GThanks for this. Yes, have a wrangler.toml at the root of the project, unchanged in the last couple of months. Has existed from the start of the project (5 months ago) with many successful builds. No pages_build_output_dir or similar
EEScratch that I think its above, its been a long day, let me check
EYep that's okay thank you!
DDoes vercel/og pages plugin exceed the 1 MiB limit?
DI am using it in Cloudflare workers and dry run shows warning about size.
JIf you're on paid, the limits are much higher now at 10MB
JHi all! I’m currently leading a project moving a docs site from Gatsby deployed on Vercel to Docusaurus deployed on Cloudflare Pages. Things have been going well, but I think I’ve hit a bit of an issue.
Is my understanding correct that I can’t make the “root” of my pages site a sub path? We would like the site to be served at
Is my understanding correct that I can’t make the “root” of my pages site a sub path? We would like the site to be served at
/docs. It’s not feasible to move the full site.
THello all - Wondering if anyone has seen feedback posted anywhere that I can upvote related to Separate Preview Branch Build Configurations? I'm using Pages to host a Hugo website. Ideally, I'd like to enable the preview branch to build with a different Hugo command line that enables the
--buildDrafts and --BuildFuture flags so that I can let stakeholders see upcoming content without needing to build the site locally. Apologies if this was asked earlier - search didn't turn up any results. Appreciate a point in the right direction to suggest the feedback to the Pages team.JIt’s been mentioned a bit before but the best solution today is to use a shell script as your build command, and then check the
CF_PAGES_BRANCH env var in it, changing the command as necessary depending on its value.
TSo
CF_PAGES_BRANCH refers to the git branch name being picked up by the build (main vs. non-main), or is it referring to the "branch" of the build in Pages (specifically "production" vs "preview")?JI believe it’s the git branch as per https://developers.cloudflare.com/pages/configuration/build-configuration/#environment-variables but it’s been a while since I checked.
KSorry for the late response @Walshy | Deploying (OOO) @Erisa | Support Engineer , I can now deploy with no issue, thank you
Ddo pages support monorepos?
DCloudflare Docs
Here are some known bugs and issues with Cloudflare Pages:
ZThey don’t with the GitHub based deploy, if you want to deploy more than one site. But you can write your own GitHub action to do wrangler deploy commands in each app to deploy in the monorepo
Dok, it seems possible if i have only one website in the monorepo, thanks
AI love Cloudflare Workers, but I am very confused by Pages. Remix.run's new Vite setup only supports Pages, not Workers (apparently based on Cloudflare's guidance). I hear that Pages is just an abstraction layer on top of Workers meant for web apps. I am frustrated by how hard it is to migrate from Workers to Pages, and I am confused that Pages made fundamentally different design decisions than Workers. QQ: Why can't there just be a flag in the wrangler.toml file that says 
Sersiously though, I would love to understand why Pages does not honor the bindings of wrangler.toml in production?
pages=true? Sersiously though, I would love to understand why Pages does not honor the bindings of wrangler.toml in production?AAlso, I can't seem to find a default/base wrangler.toml file for a pages app. Am I not supposed to use wrangler.toml at all? I think I need it for development and to define the pages "name" for CLI deployment, no?
Mwrangler.toml isn't used for pages, it's completely ignored. But only for now, very soon pages will support toml configuration
Scan i use wrangler.toml files for my pages when i commit on my branch on gitlab?
Si want to set environment variables and set
nodjs_compact and some other stuffSim currently doing it through the ui
MNo
RIs it possible to test locally having both Cloudflare Pages functions + separate Workers all under the same URL? Maybe using Wrangler ?