Do you have any experience with axiom? @HardlyWorkin'
Do you have any experience with axiom? @HardlyWorkin'
UI would just use baselime cuz its free and because cloudflare owns it now
HA little bit?
Scame here looking for this - did you find anything
Cwhat are workers>
JI didn’t find examples, but the couple threads below that message eventually got things functional
Kam i stupid or is there no button to sign up for workers paid? the one on the plans page just links me to the list of workers
Knvm found it
Khttps://www.cloudflare.com/plans/developer-platform/ possibly broken link report!!
links to "/sign-up/workers" instead of "/workers/plans"
links to "/sign-up/workers" instead of "/workers/plans"
AI see there have been some discussion about logging libraries in the past, but am wondering if anything has changed in that regard since most of the threads I find are a few years old.
Are people using some nice structured logging libraries for workers written in TS/JS? Last time I checked Pino doesn't work in CF Workers.
I don't need any transporters or other fancy stuff since I'm using the Baselime integration with tail workers. I also have the
Are people using some nice structured logging libraries for workers written in TS/JS? Last time I checked Pino doesn't work in CF Workers.
I don't need any transporters or other fancy stuff since I'm using the Baselime integration with tail workers. I also have the
otel-cf-workers
Dsanity check, if my Worker does a subrequest to another zone on Cloudflare, I can't override the cache, right?
PI need a tiny bit of 'state' between each worker run - in that I have an array of locations an an array of jobs. When a worker runs, it should pick a job and location, run a bit of logic and then 'update' the state to point to the next job (so the next worker does its work on a different job)
PDoes anybody have a good idea on how to manage this tiny state?
ZDurable objects will probably be your best bet
PHow about KVStore?
UKV wouldnt work because its eventually consistent meaning the write might not be immediately visible
PThe runner would be on a cron every 10 minutes or so, EC wouldnt matter to me I dont think
PPlease correct me if im wrong
UIts 1 minute cache so yeah wouldnt be a problem but KV is more expensive so might as well use DO instead
POk thanks for the help 
PDO is only available on paid plans - KV it is
RHello, I have the paid version on the workers platform. My CPU selection is 30,000 so last. Does this show me that it won't crash no matter how many visitors are online?
BIt means your script can use 30s of CPU time for each request to the worker, which is more than enough for a regular website.
CPU time is time spent processing stuff (example parsing JSON files), not waiting for a response from external services (such as fetching from a database).
You also need to take into consideration the memory limit which is 128 MB. It's more than enough for a normal site. You'll only run into issues if you are processing huge amounts of data like large file uploads in a bad way.
CPU time is time spent processing stuff (example parsing JSON files), not waiting for a response from external services (such as fetching from a database).
You also need to take into consideration the memory limit which is 128 MB. It's more than enough for a normal site. You'll only run into issues if you are processing huge amounts of data like large file uploads in a bad way.
PCan I use Cloudflare KV outside of workers?
PI have an app which would benefit from a simple KV solution
PBut the actual python project is too big to sit in a worker - and also isnt compatible with webassembly
Cyour options are API or Worker Proxy
API is easier, but has a global rate limit 1200 requests per 5 minutes, shared with your account including dashboard, and all request have to go back to core/no edge caching
Worker is harder and you pay per request but you get edge caching
API is easier, but has a global rate limit 1200 requests per 5 minutes, shared with your account including dashboard, and all request have to go back to core/no edge caching
Worker is harder and you pay per request but you get edge caching
PIs this for KV or the actual python project
Cwhat do you mean?
CYour python project would either use the CF API directly, or you use a CF Worker to proxy requests to the KV binding, bound to that worker
PI'm confused as to what you're talking about regarding 'your options are API or Worker Proxy' - do you mean as a replacement for KV or where I should host my Python project
PAgain, the CF Workers require a build to webassembly - some of the packages I'm using cannot compile to webassembly
CI mean as a way to access Cloudflare KV
Cyou host your python project wherever, and either you call the CF API to use KV, or you call a worker you make to access KV, both have different benefits/downsides
P
CThat's using the CF API, so you have those downsides as noted above
global rate limit 1200 requests per 5 minutes, shared with your account including dashboard, and all request have to go back to core/no edge caching
PI dont care so much about edge compatibility - it's only ever going to run on a single instance
PThe python project is only ever going to run once per 10-15minutes
Cthen sounds like that could work for you
PI dont really see how workers can ever be used for anything more than returning 'hello world'
PLiterally every package I've tried to use requires me to 'request availability from cloudflare team'
Ctalking about python workers? Yea they're still very much in beta, JS workers are recommended and probably will always be the most supported
PWell yeah I tried using Rust workers, which tbh is in even more of a beta
PBoth Rust + Python gave me a bad experience
CYea, JS/TS is just best for workers. I mean it all runs on V8 JS Engine - same as Chrome, Both Rust and Python are just running as WASM and binding back to javascript methods/it's all still JS at the start and finish
RI have max 10mb files but what is the bad usage?
I?channel-crossposting
FPlease do not post your question in multiple channels per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.R#stream-and-calls
IYou probably want to move to #stream-and-calls yeah.
