this is so well priced I'm almost wondering what the catch is or maybe I'm just too used to AWS..
this is so well priced I'm almost wondering what the catch is
or maybe I'm just too used to AWS..
or maybe I'm just too used to AWS..
https://api.cloudflare.com/client/v4/accounts/${process.env.ACCOUNT}/workers/scripts/${"worker-name"}/content?https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/workers/dispatch/namespaces/$DISPATCH_NAMESPACE/scripts/$SCRIPT_NAME/content insteadclass UserDurableObject extends DurableObject<Env>?send_email binding. What would a secure setup look like where the email goes through the dispatch worker, and for any user worker supporting email, it would pass it on to be handled by the user worker?wrangler dev session for "customer-worker-1" in namespace "test" to proxy to
wrangler dev session for "customer-worker-1" in namespace "test" to proxy tonpx wrangler@dispatch-namespaces-dev to start user and dispatch workers?
Workers Free plan: Only Durable Objects with SQLite storage backend are available.
new_sqlite_classes in migrations, not new_classes{
"name": "cashmoney",
"compatibility_date": "2025-04-03",
"compatibility_flags": ["nodejs_compat"],
"observability": {
"enabled": true,
"head_sampling_rate": 1
},
"assets": {
"not_found_handling": "single-page-application"
},
"main": "./worker/index.ts",
"migrations": [
{
"new_classes": ["Arenas"],
"tag": "v1"
}
],
"durable_objects": {
"bindings": [
{
"class_name": "Arenas",
"name": "ARENA"
}
]
},
"vars": {
"UPSTASH_REDIS_REST_TOKEN": "YOUR_TOKEN",
"UPSTASH_REDIS_REST_URL": "YOUR_TOKEN"
}
}