"Cloudflare webhook is being called multiple times, and builds are being created repeatedly. Is ther
"Cloudflare webhook is being called multiple times, and builds are being created repeatedly. Is there any way to stop this?"
*.domain.com/* i get AAAA towards 100::, Proxied ( :cloudflare: ).*.*.domain.com, this is not possible for a single SSL/TLS certificate due to inherent TLS protocol restrictions. You will need to issue a new certificate (or hostname for existing certificate) for each first level wildcard e.g. *.org1.domain.com, *.org2.domain.com and so on.scriptname-username.example.com to bypass this
‘User Workers’ meaning… These would be workers that I am deploying on behalf of the customer… do customers have visibility of these workers/source code from their dashboard? I presume not (I would hope)
D1 and R2 access from these User Workers… this would be to MY instance yes? And I would be responsible for ensuring segregation of data as appropriate?
Placing limits for customers… This would be something I would need to implement myself from the dispatch worker correct?
tag (not tags) field on the script object?*.domain.com/*100::*.*.domain.com*.org1.domain.com*.org2.domain.comscriptname-username.example.comexport default {
async fetch(request, env) {
try {
let workerName1 = "worker1";
let userWorker1 = env.dispatcher.get(workerName1);
let result1 = await userWorker1.fetch(request);
let workerName2 = "worker2";
let userWorker2 = env.dispatcher.get(workerName2);
let result2 = await userWorker2.fetch(request);
} catch (e) {
if (e.message.startsWith('Worker not found')) {
return new Response('', { status: 404 });
}
return new Response(e.message, { status: 500 });
}
},
};