C
Gwrangler dev is your command, yeah?
HThe auto-reload logic is in wrangler, so if you are going straight workerd, you will have to manually restart on every change
HNot that I know of
Nhey, I'm trying to have a basic database setup, but wanna skip D1 because of the location limitation.
KV works, but as it gets more complex, only having k=v is not great.
is R2 or durable objects maybe what I'm looking for?
KV works, but as it gets more complex, only having k=v is not great.
is R2 or durable objects maybe what I'm looking for?
CDepends what you mean by "location limitation" Any location limitation D1 has is from the fact it uses Durable Objects (DOs) which only run in a few locations https://where.durableobjects.live/, and each DO only exists at one of those locations. R2 uses DOs as well for all the metadata, and of course DO has those same limitations too, unless you implemented your own replication across DOs or something
NThanks for the quick response. I want to use cloudflare workers to be globally fast for my licensing system for a software product.
NLooks like KV it is
IIs is possible to set a custom version id / deployment id during e.g. build time and then communicate that with cloudflare to be deployed under that version / deployment id?
Wyou cannot control the version/deployment ids no.
IThanks! Think you might already understood from a similar question in #pages-discussions, I was looking to prevent version skew, saw that Gradual Deployments support Version Affinity and / or Version Overrrides, which could potentially solve this.
.Bump. My code seems to just hang and do nothing, but running it elsewhere works
RHello, I have the paid version of cloudflare workers, but when I receive too many requests, I encounter the 429 too many request error?
RShould I buy Workers for Platforms to prevent this from happening?
Ehttps://developers.cloudflare.com/workers/platform/limits/#request
Cloudflare’s abuse protection methods do not affect well-intentioned traffic. However, if you send many thousands of requests per second from a small number of client IP addresses, you can inadvertently trigger Cloudflare’s abuse protection. If you expect to receive 1015 errors in response to traffic or expect your application to incur these errors, contact Cloudflare support to increase your limit. Cloudflare’s anti-abuse Workers Rate Limiting does not apply to Enterprise customers.
Etldr, contact support
RCloudflare does not respond to the issues I open in support. This is taking too long.
RI don't get error 1015, I get 429
RCPU count limit is 30,000
DHi I'm considering using a DO in my app architecture and I'm curious about the physical location of a DO. I have some AI/GPU servers across the US and those servers need to receive messages from clients and also maintain some state for each connected client. My API runs on Workers and my client app is a JS app running on browser and in webView on desktop. I know with many/most of the CF services, workers run on the CF edge close/closest to the user. So, in my application when a client starts a real-time session with my backend, I'm assuming my Worker will create a DO that also lives close to the user / close to where the worker is physically located. Is this true? My application is real-time streaming / interaction (similar to a cloud gaming and streaming application) and so my GPU servers will be near most major markets in the US. My initial thought is to do a "ping" to all my GPU server locations and pick the one that is fastest when my worker gets the initial "create session" request. Therefore, is it true that the DO I then create would be somewhat close to where the Worker is executing and thereby close to my user's location?
DTracking where Durable Objects are created, wherever you are in the world.
Dhmm, after looking at that map, since my application is more like real-time cloud gaming setup where latency is key (at least 30fps for most customers), seems i may have to do some serious testing of DO to know for sure whether it will be physically close enough to my users. But, looking at that map, I'm thinking DO's wouldn't be close enough to maintain super low latency for my app. That's ok if so, I can just use WebSockets in a Worker and maintain state within the WebSocket Worker I believe....
Nhyperdrive seems to replace all query params with sslmode=disable
Nat least in dev
Ncant connect to neon.tech
Nworked around with this
Nnvm .seems not to connect to the database
Njust times out
Sany way to use nodemailer on a CF worker?
NAny way to upgrade Cloudflare Worker plans with crypto? PayPal isn’t an option in my country
Enope, credit/debit card and paypal are the only options
Eif you cant do either of those then you cant upgrade unfortunately
NLol
Jis their a way to run a program ever hour?
HCloudflare Docs
Enable your Worker to be executed on a schedule.
ĐI couldn’t sign up for the paid worker plan. Has anyone else experienced this issue?
.What's this?
.Alright ok
DHey @Đăng Bùi.C @Pelps ,
Could you open a billing support ticket so the team can look into this for you?
Unfortunately this is outside of what we can help you with on Discord - and unfortunately billing support has quite a long queue so you might need to wait a few days before you hear back
Could you open a billing support ticket so the team can look into this for you?
Unfortunately this is outside of what we can help you with on Discord - and unfortunately billing support has quite a long queue so you might need to wait a few days before you hear back
D?billing Here's how to open a billing ticket:
FCloudflare's billing system is undergoing some changes/migration. During this period, you may notice extra bills, incorrect bills, or other issues.
To resolve these issues, create a Support ticket by using the following link (you must be logged into your Cloudflare account): https://dash.cloudflare.com/?to=/:account/support
Note that all accounts, even Free plan accounts, can create billing tickets. Tickets are the only way to resolve billing issues; we cannot help you in this Discord.
To resolve these issues, create a Support ticket by using the following link (you must be logged into your Cloudflare account): https://dash.cloudflare.com/?to=/:account/support
Note that all accounts, even Free plan accounts, can create billing tickets. Tickets are the only way to resolve billing issues; we cannot help you in this Discord.
DYou can try using the
--minify option to reduce your worker's sizeDpotentially, could be worth a shot