just doing a "return new Response(JSON.stringify(context.env), { status: 200 });" and everying shows
just doing a "return new Response(JSON.stringify(context.env), { status: 200 });" and everying shows up exept my [vars]
Cin toml
Ci dont have any special envioments configued, just using top level
WWhat's your wrangler.toml
C[vars]
API_HOST = "example.com"
API_HOST = "example.com"
Cwell
Cname = "my name of project"
pages_build_output_dir = "./public"
compatibility_date = "2024-03-29"
compatibility_flags = ["nodejs_compat"]
send_metrics = True
[vars]
API_HOST = "example.com"
pages_build_output_dir = "./public"
compatibility_date = "2024-03-29"
compatibility_flags = ["nodejs_compat"]
send_metrics = True
[vars]
API_HOST = "example.com"
Cand d1 and r2 connections
WWhat's the full
Cmessage.txt350B
WThat looks alright, do you see the bindings in there?
Cmessage.txt155B
Cis the response
Cwhen doing this
Cany tips?
Wlooks fine... i'm gonna be going to sleep here in a few - i'd recommend making an issue on workers-sdk
Cokok, thx tho
Sanyone managed to get react-helmet-async running on CF Pages?
or is there any alternative that runs on CF Pages through functions?
or is there any alternative that runs on CF Pages through functions?
IIs it possible to manually capture sentry errors or increment metrics from a function? I can do it on the front end, and with the pages plugin/middleware thing I can capture exceptions, but manually capturing with like Sentry.captureMessage (using the react SDK) doesn’t work. Is there a different sdk or even an api wrapper I can use for that?
Hnpm
Offical Sentry SDK for Cloudflare Workers and Pages. Latest version: 8.26.0, last published: 5 days ago. Start using @sentry/cloudflare in your project by running
npm i @sentry/cloudflare. There are no other projects in the npm registry using @sentry/cloudflare.
IOh perfect, not sure how I missed that. Also I didn’t see the D1 instrumentation thing, that’s great! Thanks.
IIs this package not supposed to be used anymore:
@cloudflare/pages-plugin-sentry?II keep getting the error
Argument of type 'string' is not assignable to parameter of type 'MetricsAggregatorConstructor'. when using the exact same metrics function in that sdk as the react sdkIit doesnt like the string for the metric id/name
LHey all, I'm using a function to call an api and return a daily timetable. I really only need to call this function once a day to get the latest timetable, but from my understanding, the way functions work is that the api will get called with every request.
I've tried using the cache api, but that doesn't seem to completely help since the cache only occurs at the originating data center.
What is a better way to handle a single daily request to an api using cloudflare functions?
I've tried using the cache api, but that doesn't seem to completely help since the cache only occurs at the originating data center.
What is a better way to handle a single daily request to an api using cloudflare functions?
LI really only want to call the api at some predetermined time, build my page and then have that static page be served for 24 hours until it's time to call the api again and update the page.
LIs there a way to do that with cloudflare functions?
LBump
IFunctions cannot be triggered on a schedule. For that you'll need a Worker with a cron trigger.
LThanks @Isaac | YYZ01, EWR01 . Is there any documentation on how to use a worker to update a pages project? I'm struggling to wrap my head around how my worker can tie into routing and updating a page at a specific route.
HYou can use a Deploy Hook to rebuild your Pages Project. Create a Worker, then have it run a cron once a day that just calls your deploy hook
Cloudflare Docs
With Deploy Hooks, you can trigger deployments using event sources beyond commits in your source repository. Each event source may obtain its own unique URL, which will receive HTTP POST requests in order to initiate new deployments. This feature allows you to integrate Pages with new or existing workflows. For example, you may:
EFor functions, how come it doesn't work with Astro SSR on Cloudflare pages?
Eheres my directory structure
EI'm using Astro with the Astro API Endpoints, but I also want to use serverless cloudflare functions.
EPretty much all the API Endpoints are on the
/~api route, but I want the cloudflare functions to be on /~fn
Eany update on this? I'm not even sure if I should be using pages functions and the Astro API endpoints at the same time
HWhen using Astro SSR, then you must use Astro’s system for API Endpoints. You can’t mix with Functions routing
EOk thanks
EDoes each Hono route in a Cloudflare Pages app translate to a Cloudflare Pages Function?
Ereason i am asking is that i dont want my instance to get clogged if the entire Hono app goes inside a single worker
EWith Astro, I can see on the page that this basically confirms that each Astro API Route is a different pages function. I don't know whether the same is true for Hono
EAnd id much rather use pages functions to keep something in my project rather than making a separate worker for each thing
Eso each endpoint runs as a separate pages function, right?
L@HardlyWorkin'
LHelp me domain pending
I?pings
FPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
WIt is all a single worker. Putting these all into like 20 different workers would be much more complicated and slow
Whats the concern over a single?
Whats the concern over a single?
