JHeadless browsers for tasks like web scraping with proxies, for example, residential proxies
HCloudflare Self-Serve Subscription Agreement 2.2.1 Restrictions
Unless otherwise expressly permitted in writing by Cloudflare, you will not and you have no right to:
...
(j) use the Services to provide a virtual private network or other similar proxy services.
This page is for those who are interested in our Self-Serve Subscription Agreement.
Cthe template for nextjs on pages doesn't deploy
C
Cneed your feedback related to the following: i'm having a sass where each tenant uploads some images. what should i use, r2 or images ?
BHi team, with Workers routes (pattern matching) is it intended behaviour for a wildcard to match a query parameter of a different base URL?
E.g. with a route pattern of
That pattern actually matches the following URL:
It's matching the query parameter.
Workarounds?
E.g. with a route pattern of
*.domain.com/* (to match wildcard subdomains)That pattern actually matches the following URL:
https://otherdomain.com/api/etc?redirect_uri=https://example.domain.com.It's matching the query parameter.
Workarounds?
BEven the route pattern 
https://*. domain.com/* is matching against URLs like https://otherdomain.com?redirect_uri=https://domain.com 
TGetting a vague
Failed: error occurred while installing tools or dependencies error with Workers Bulds :/ any ideas?
TAlso it doesn't detect the pnpm version from package.json
packageManager which is annoying. PNPM_VERSION env var also isn't documented https://developers.cloudflare.com/workers/ci-cd/builds/build-image/Cloudflare Docs
Understand the build image used in Workers Builds.
Esorry for ping but I wanna do the same, are you broke yet? :D
EI also have something similar for discord but I decided to spin up a VPS for discord events because undici doesn't work well from DOs and also I heard Discord throttles cloudflare servers or something (dunno if myth)
EFor anyone interested: one VPS per 1k servers ish, gets all discord events then forwards to DOs through websockets
- 1 DO per channel
- 10s idle timeout on websocket connection
Chey, what's the fastest/cheapest way to use images with a qwick/astro worker?
QHello everyone. Is it possible to skip worker processing for certain urls?
for e.g. I want the worker to work for every url like *.example.com but not for app.example.com and api.example.com
how can I achieve this. I am stuck!
for e.g. I want the worker to work for every url like *.example.com but not for app.example.com and api.example.com
how can I achieve this. I am stuck!
Ego to https://dash.cloudflare.com/?to=/:account/:zone/workers for the domain, and configure the worker routes like this by selecting "None" as the worker for app. and api.:
E
MI'm deciding between using a selfhosted postgres db (where storage space/cost is a non-factor, and its a proper rdbms) vs using cloudflare d1 (scales to 0/no maintenance/no backups needed/etc). Does anyone have any input or experience that may be helpful?
JI’d go with pg + hyperdrive if you want some latency reductions + caching. I can’t safely recommend D1 for production use. https://github.com/cloudflare/cloudflare-docs/issues/18485
Tare there any blogs that go over winning combinations of cloudflare workers products for different use cases?
Twith so many options sometimes it’s hard to choose
CCloudflare Docs
Storage and database options available on Cloudflare's developer platform.
Tyooooo thanks!!
JI'd go with something external like Neon for PG which also has a generous free tier, or Turso for SQLite.
EI'd also recommend PG, I use supabase but am considering moving to neon (haven't decided yet)
JDirect database connections are absolutely possible with workers nowadays
JYou can use Postgres.js just fine, for example. It uses cloudflare:sockets under the hood
JA package needs to be built for it, but there are many common ones that already use
cloudflare:sockets to talk to DBs today, like postgresEi use hyperdrive myself, works very well
Evia drizzle
EJI'd drop the
prepare: false these days - hyperdrive is well optimised for prepared statements, but yes exactly. Drizzle + postgres + hyperdrive on Workers is awesome.Ecool, will try updating that! i had been having some errors with prepare that's why I disabled it before
JThere were definitely issues some months ago, but that's long since been fixed afaik. I don't use
prepare: false in my stuff and haven't seen any issues yet.JDrizzle can, yes. The example above from Ephemeros is showing exactly that
JI also run Drizzle with Postgres in many Cloudflare Workers
Ti need more ): it didn’t go into architecture designs like i was hoping it would
I^ What James said, this was confirmed by an engineer on the Hyperdrive team a few days ago when it came up, so yes, you should be good to use
prepare: true or omit it because it defaults to trueNeon’s serverless driver was useful before Workers could connect to DBs directly. Nowadays I’d recommend just the
postgres library paired with Hyperdrive, and then you can use your ORM library of choice like drizzle or prismsJDon’t bother with the “integrations” in the dashboard
JYep - just
postgres - Neon pooler URL would be my recommendation then
His it against cloudflare worker terms of service
to have a singnalling server like https://github.com/gfodor/p2pcf and have multiple members of a community host a version on their cloudflare account
the web app will look for one of these cloudflare workers that is active and connect using it
to have a singnalling server like https://github.com/gfodor/p2pcf and have multiple members of a community host a version on their cloudflare account
the web app will look for one of these cloudflare workers that is active and connect using it
GitHub
Low cost, low effort P2P WebRTC serverless signalling using Cloudflare Workers - gfodor/p2pcf
Hi am afraid it might be abusing the free tier so i had to make sure
JI would forego using
@neondatabase/serverless and just use postgres if you can - it doesn't provide much benefits nowadays.JBut generally no, you will not be able to define and connect to the DB outside of your fetch function
JA common approach to this is something like a
useDB function that you pass in your envhonoAnother approach would be to throw it into AsyncLocalStorage, but that's a litle more complex: https://developers.cloudflare.com/workers/runtime-apis/nodejs/asynclocalstorage/
SDoes anyone have any insight on the perf characteristics of workers when you have a larger (a few megabyte) codebase? Since its serverless, how does it get loaded? Do the workers get "prewarmed" and ready to handle their request, or is it just in time (so if there's a lot of javascript to load to serve a single request, your workers are gonna be slow?). Its not obvious to me exactly how they work.
KPrewarmed during TLS handshake, but otherwise loaded upon request and hang around for awhile for other requests till evicted (i.e resources needed for other Workers or runtime update)
https://blog.cloudflare.com/eliminating-cold-starts-with-cloudflare-workers/
https://blog.cloudflare.com/eliminating-cold-starts-with-cloudflare-workers/
The Cloudflare Blog
A “cold start” is the time it takes to load and execute a new copy of a serverless function for the first time. It’s a problem that’s both complicated to solve and costly to fix.
Qthanks. I'll check
BCurious if you were able to figure this out? Still facing the general issue of not being able to set the old headless mode.