Rok... thanks
that's kinda impractical for my usecase though.
i think i'll just answer with 403s instead.
thanks anyway!
that's kinda impractical for my usecase though.
i think i'll just answer with 403s instead.
thanks anyway!
CHey, I am trying to send an email with a cloudlfare page function. I am following this tutorial https://developers.cloudflare.com/email-routing/email-workers/send-email-workers/ for the new email workers but im stuck -- it says to put something in a wrangler.toml file, but there is no wrangler.toml file in cf pages? where do i put it instead?
You can send an email about your Worker’s activity from your Worker to an email address verified on Email Routing. This is useful for when you want to …
KYou can't use
send_emailok:(
Cthanks though. I will then use a worker until this works
SHey all, using SvelteKit in Cloudflare Pages/Functions, and running locally via
wrangler pages dev -e dev -- vite devLocationX-Sveltekit-Page
Uyes
UIf you want to actually have a reliable contact with the team you should talk with sales about an enterprise contract. But there are employees and community members that answer questions in #stream
Acan I create a service binding to another worker (not a DO, just a worker) for a cloudflare pages function worker?
JHey folks, how do I bind the new hyperdrive service to my Page functions? I don't see an option in the UX to bind it for production.
JUnfortunately you can't today. Pages doesn't support Hyperdrive, nor the
node_compat build you need for most (all?) drivers that work with Hyperdrive today
JI actually got the Postgres lib driver working today with a few hacks.. should have it ready by the weekend to release
JNice!
Gis there an alternative to file I/O for nodejs projects?
GMy project is in SvelteKit and I use a lib that, unfortunately, only accepts input as a file path and outputs to a file.
GI use the
node:fs library as of right now. is there any alternative that can work on Functions?
HInput as a File object, or a file path?
Gpath
Gif it were an object, I wouldn't need to do file I/O haha
GOh wait nvm I see wym
HYeah, then short of trying to rewrite all of the fs calls to R2/KV/whatever, there isn't much you can do
GOh I can work with R2
Gbut that'll butcher local testing
Gwhenever I test it will push to R2 haha
Gbesides, that's a ton of overhead, isn't it? since I'm almost instantly using the outputted files
GHOh wait, weren't you the person who was trying to use the
prince lib which calls the CLI to generate PDFs from HTML?Ghaha yes
GI'm trying to eliminate each roadblock from hosting on Pages one at a time
GAFAIK
prince should work on PagesGit brings its own binary
ZJust like workers, pages functions don't run on Node, and they don't have access to the operating system. You can't run binaries on pages functions. You could, however, run stuff like that during build
ZWell, I suppose if it's compiled to WASM it might work, but if that's not supported adding that yourself will be extremely tricky
GFair enough.
GI can run them on normal Pages though, right?
Greferring to binaries specifically
GAFAIK, I can't run stuff on Node on Pages either
ZPages is a static file host. Pages functions is workers integrated with pages. Neither of these can run node. Pages also has a build process (you push a change to git -> CF builds the project and uploads the results to pages). This runs in a VM where you can do whatever you need, including running node or other binaries. You can't trigger this build process per request.
GThanks for the detailed explanation!
GNeither of these can run nodethis refers to functions and workers, right?
ZI was referring to the static file hosting part of pages and the pages functions part of pages. But indeed, workers also can't run node or executables
GSo, I can only run node and binaries during the build process and not at runtime? (of Pages, not Functions)
