Can I add my own defined variables to the env file?
Can I add my own defined variables to the env file?
HLike a secret, or a regular env variable?
Peither/or?
HOh wait, this is pages. Then yeah, just put them in your .dev.vars
PIf you see my name it's always pages 
MIf I made a function in a pages app using nextjs to query a D1 instance, how would I call the function? Would I just export it like a regular function or would I have to fetch the endpoint.
KAre you on an Enterprise plan with Bot Management? If not, those req.cf options are dummy values
D1.. Using "URI Path" could be a better choice here.
But I would personally try something like "URI Path", "does not start with" and "
On the other hand, if that specific Configuration Rule is meant to be the Configuration Rule that has the effect for "
- For "URI Full", you need to have "
" in front of thathttps://
, exactly as it shows it says in the example below the input field.example.com - I'm under the impression that you CANNOT do asterisk/wildcards, and that the trailing "
" therefore is useless, and that the "URI Full" will never be functional, according to your example.* - "does not equal" would, considering the two ones above, require an exact match. Perhaps you also need to change "does not equal" to e.g. "does not start with".
/api/But I would personally try something like "URI Path", "does not start with" and "
/api//api/On the other hand, if that specific Configuration Rule is meant to be the Configuration Rule that has the effect for "
/api/
Sstarted to see a 'Worker exceeded resource limits' today, don't understand why - it looks like it's the CPU but not sure
KHow does this prevent a bot from doing a direct POST to my endpoint?
Your endpoint sends the widget response from Turnstile to the siteverify endpoint to validate it is valid and the user passed the challenge.
https://developers.cloudflare.com/turnstile/get-started/server-side-validation/
BI have a quick question around functions. Are they reused between multiple requests? If I set a global
Loggerctx.waitUntil(logger.flush())
HIt may be reused, but there isn’t any guarantee
SI have a site where I want to use functions to store information from a form into a database, where should I look to learn how to do this
Dhey, i'm new to cloudflare and i'm trying to create a project with next.js and cloudflare by using the command in the documentation ( npm create cloudflare@latest -- --framework=next ) after that i need to use cloudflare API routes not next API routes, how to do that
DI made a functions directory and wrangler.toml in the root, but when i'm trying to run the localhost development it gives me an error (Must specify a directory of static assets to serve or a command to run or a proxy port.)
Di kbow it's a basis question but i need someone to help me know how to implement and use cloudflare API routes in next.js application
DYou can only use it when you are doing a static build of your application. For server side components and next js api routes, you need to build it using next-on-pages cli
KWhat does
https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/get-identityShould have an
email
Dhmmm, coming from AWS. how would i create an api for my application on CF? i was assuming i would see an API Gateway in my dashboard for my site... but API GW is only for enterprise customers?
HYou would just write the API in JS, deploy it to Workers, then assign it to your domain
HOr well, you can write your API in another language if you want
Dand a little reading it seems you can assemble an API through this? - create a DNS for your api.domainX.com - create a Pages Function or Worker - assign a routing for that / those functions?
Dok @HardlyWorkin' , so i should look into Workers
Di see
Dthanks!!
Dwhat's the high(est) level difference between using a Function or a Pages Function for my API middleware code?
Der i'm sorry, a Worker*
HA Worker and a Function?
Dright,
HA Worker can do more. It’s usually the first to get new features/bindings. Functions are basically Workers with Pages integration. Functions are deployed as part of a Pages project, along with your static assets. Said assets are served for free
Di see
Dso Workers == AWS Lambda and within the setup/config of a Worker, you can define your API domain / paths / routing / etc
HYes, sort of
HWorkers are also a lot cheaper, but restricted in what they can run
Dand a Pages function is part of a full stack deploy / repo / project where your site/pages/assets + some backend code that you need to be accessible by some endpoint would live all together as a project/repo and when you deploy that full stack, it's treated as CiCd pipeline, etc
Dok, off to read Workers docs, thanks @HardlyWorkin'
SWhere can i ask about dns?
H#general-help or #general-discussions
SThanks
《Hi all, I'm just attempted a POC, and I'm running into a couple of problems around the functions.
I create a new nuxt app using the create-cloudflare CLI 'create-cloudflare nuxt3-poc-002 --framework nuxt --ts true', and I add the ./functions folder, and copied the helloworld.js file from the docs.
I ran npm run pages:dev, and navigated to localhost:3000/helloworld. The app keeps returning a 404, and not returning the expected response stated in the documentation here. https://developers.cloudflare.com/pages/functions/get-started/
Is there something I'm missing here? I assume the npm run pages:dev also hosts the functions worker as well?
EDIT:
I have created 2x POC now. One is purely the create-cloudflare built app. That returns a 200, and just returns a standard page.
I have a more advance version where I have added layouts, and pages, and that returns a 404. So I'm assuming the pages automated routes are handling/hijacking the API requests, and returning the 404... Still I would expect the pages:dev command to run the worker and proxies as it worked in the cloud.
If I take another approach, I run 'npx wrangler pages dev ./functions' within the root of the website, and it'll start hosting the functions worker on 127.0.0.1:8788.. and if I navigate to 'http://127.0.0.1:8788/helloworld' I see the results expected. So there is no problem compiling the functions code.. I assume the nuxt router is hijacking the handling of the request away from wrangler's worker hosting, and the functions logic never gets hit.
Again this doesn't make sense to me. I wouldn't want to need to make a proxy via axios or anything to get this working. As I would expect it to work out of the box as is. Since it's a create-cloudflare CLI generated project..
I really want to use the SSR features of Nuxt locally.
I create a new nuxt app using the create-cloudflare CLI 'create-cloudflare nuxt3-poc-002 --framework nuxt --ts true', and I add the ./functions folder, and copied the helloworld.js file from the docs.
I ran npm run pages:dev, and navigated to localhost:3000/helloworld. The app keeps returning a 404, and not returning the expected response stated in the documentation here. https://developers.cloudflare.com/pages/functions/get-started/
Is there something I'm missing here? I assume the npm run pages:dev also hosts the functions worker as well?
EDIT:
I have created 2x POC now. One is purely the create-cloudflare built app. That returns a 200, and just returns a standard page.
I have a more advance version where I have added layouts, and pages, and that returns a 404. So I'm assuming the pages automated routes are handling/hijacking the API requests, and returning the 404... Still I would expect the pages:dev command to run the worker and proxies as it worked in the cloud.
If I take another approach, I run 'npx wrangler pages dev ./functions' within the root of the website, and it'll start hosting the functions worker on 127.0.0.1:8788.. and if I navigate to 'http://127.0.0.1:8788/helloworld' I see the results expected. So there is no problem compiling the functions code.. I assume the nuxt router is hijacking the handling of the request away from wrangler's worker hosting, and the functions logic never gets hit.
Again this doesn't make sense to me. I wouldn't want to need to make a proxy via axios or anything to get this working. As I would expect it to work out of the box as is. Since it's a create-cloudflare CLI generated project..
I really want to use the SSR features of Nuxt locally.
GHi there. Can someone provide me a simple code on how to access env variables that is already set in CF dashboard and return it using Functions.
Thanks in advance.
Thanks in advance.
《export async function onRequest(context) {
const myVar = constext.env.[your-envirment-variable];
console.log("myvar = '${myVar}'");
// Note: I'm not sure the console will return value because of security settings. So you might need to do some trick to get pass that. So it might seem like nothing is returned if your logging it out. But if you combine it into an other object it should get around it so you can see it in the logs.
}freehanded that code, so just check it.
You'll also need to edit your wrangler.toml files to have the vars in there, even if you have configured them in the dashboard. That lets the services know it should look for them.
[./wrnagler.toml]
[vars]
myVar = "somthing"
《BUMP. Anyone know how to combine this hosting so I don't need to setup some weird proxy thing for local development?
GI have tested this and it works even without updating toml files.
