Emil Lerch
533ab89fe9
The wrangler project does some bundling for us, that we are not ready to reproduce here. So for the time being, we will do this manually
29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
Upload worker to CloudFlare
|
|
===========================
|
|
|
|
Until we're better
|
|
------------------
|
|
|
|
1. Add `accountid.txt` to `src/` with the CloudFlare account id
|
|
2. Add `worker_name.txt` to `src/` with CloudFlare worker name
|
|
3. `zig build run`
|
|
|
|
Getting new index.js
|
|
--------------------
|
|
|
|
* Run a real wrangler deploy, then go into the console and copy/paste
|
|
|
|
Steps we take:
|
|
--------------
|
|
|
|
1. Check if the worker exists:
|
|
GET https://api.cloudflare.com/client/v4/accounts/<account id>/workers/services/<worker_name>
|
|
404 - does not exist
|
|
2. Add the "script"
|
|
PUT https://api.cloudflare.com/client/v4/accounts/<account id>/workers/scripts/<worker_name>?include_subdomain_availability=true&excludeScript=true
|
|
3. Get the "subdomain". I believe this is simply to determine the test url:
|
|
GET https://api.cloudflare.com/client/v4/accounts/<account id>/workers/subdomain
|
|
4. Enable the script: This is **only** done if the script did not exist. Subsequent flows leave this alone
|
|
POST https://api.cloudflare.com/client/v4/accounts/<account id>/workers/scripts/<worker_name>/subdomain
|
|
Data: { "enabled": true }
|