You can't point to remote KV namespaces when running in dev.
You can't point to remote KV namespaces when running in dev.
BNot even to preview namespaces? Do you have to set them up in a wrangler.toml file to have kv's locally then?
HNope. Only Workers can access remote KV.
pages devwrangler.tomlWhat sort of approach would you take to simulate a dev environment locally? I want to speed up my dev process because it's getting tedious waiting for a new build each time I'm testing
HFind the data you need to get it running from your remote KV namespace, then add it locally with
wrangler kv:key put --local
VHow can I serve a common html file say 'foo/index.html' for URLs matching '/foo/*', similar to CF do for '404.html' but without the 404 status? Is it a way to make it possible in pages itself, without the assistance of wranger?
VIt will redirect to /foo/, but that's not the required result.
It should just load the
It should just load the
foo/index.html at /foo/* itself without any url redirect.BThanks! This solved my issue. I'm looking at using the --persist-to flag to make it easy for multiple developers to set the environment up. To use the values saved with the --persist-to flag, do you know if you need to specify using that as a namespace when running wrangler pages dev?
HNo, it should run based ont he binding name.
SI'm trying to setup a page rule to redirect www. to our root domain on a pages project but it doesn't seem to work, am I missing something simple?
MHello! I have a site hosted on CF pages and some people are reporting that they can load my site. If changing internet connection works. Has anyone ever experienced this?
MWe transform ideas into digital experiences that connect with your audience and help you build your dream team. Let's work together to create something remarkable?
MMy problem is basically the same, but there is no resolution:
https://community.cloudflare.com/t/site-is-not-accessible-via-some-internet-providers/382528
https://community.cloudflare.com/t/site-is-not-accessible-via-some-internet-providers/382528
Cloudflare Community
Hi, I have several sites hosted in a cloud server at IONOS with CF. Just two of them when CF is enabled they are not browseable trough the ISP NET/Claro (Brazil). Is there anything that I can do to fix this? When I disable the CF trough DNS I can access these ones. Regards,
Sis it just outright stupid to have a server-rendered next.js app on cloudflare pages and a separate backend on cloudflare workers or are there valid reasons to use such an architecture?
S
JMaybe don't use
https:
SI can try, but I recall the rule makes you include http or https
JI use Bulk Redirects and don't need
https:
FHey guys! I'm having trouble accessing PlanetScale from within Cloudflare Pages
Fdid anyone ever fiddle with that?
IHello, is there anyone that can hop on a call to help me fix this Error code 522 issue because I have tried everything and it cant seem to be fixed.
CIs this with a custom domain?
II guees yeha
Iyeah
CDid you go through the process in pages or did you manually add a CNAME record to your zone?
IManually
CYou need to go through the process or it will 522
From the docs:
From the docs:
To ensure a custom domain is added successfully, you must go through the Add a custom domain process described above. Manually adding a custom CNAME record pointing to your Cloudflare Pages site - without first associating the domain (or subdomains) in the Cloudflare Pages dashboard - will result in your domain failing to resolve at the CNAME record address, and display a 522 error.
Chow can I get the cf properties in request on next edge route?
ADoes anybody know if middlewares should work locally with
wrangler pages dev
EWhere in dash.cloudflare.com would I inspect 500s from my page workers?
EAnswer: in Deployment details under functions.
EIs it possible to have a NodeJS queue worker inside of the pages/functions project or does it need to be it's own standalone NodeJS project?
HIt can't be Node at all. It has to be written for Workers.
EAre the functions in a pages project technically considered workers or is it a different runtime?
HNo, I mean that while you can submit tasks to a Queue with Functions, they cannot be a Queue Consumer. You have to deploy a separate Worker to consume Queue events.
EDo you know of any techniques to have queue producers via page functions and consumers share common code, specifically in TypeScript? My queue consumer needs to know about the same schemas as my queue producer and ideally would be able to load the same utils.
I've been able to do this with AWS Lambda, albeit non-trivially, but it helped reduce extra work and many headaches in the long run.
I've been able to do this with AWS Lambda, albeit non-trivially, but it helped reduce extra work and many headaches in the long run.
HYou could have the Queue Consumer in the same Repository, and then import the schemas into both the producer and consumer?
BAnybody else having issues with pages atm? our commits are not getting built/deployed
Bguess github is having issues, may be related
BWelcome to GitHub's home for real-time and historical data on system performance.
ZPreviously when GH had a webhook issue, pages projects were also not deploying, so it's likely related.
EYes, that would do it
EYep, also experienced a pretty long (felt like 30 min) lag.
EIs lerna (https://developers.cloudflare.com/workers/tutorials/manage-projects-with-lerna/) the right tool for this or is there a more simple approach?
All of the tutorials assume you have already completed the Get started guide, which gets you set up with a Cloudflare Workers account, C3 , and …
HJust have a
sharedIt would be ideal if everything could share the same
package.jsonIf the package is in the root of the repo, then it should be applied
