syntaqxEvery sandbox on g1t's runners has 20 GB of disk, the most Cloudflare Containers give one, as much or more than a GitHub-hosted ubuntu-latest's 14 GB: the standard machine (ubuntu-latest and every other hosted label, and all other work) becomes a custom instance type of 1 vCPU, 4 GiB and 20 GB, where standard-1 had half a vCPU and 8 GB, and g1t-2core a custom 2 vCPU, 8 GiB and 20 GB, where standard-3 had 16 GB; g1t-4core stays standard-4, which already had 20 GB. 1 vCPU is the smallest a custom type may have, and Cloudflare bills CPU only as it is used, so the doubled vCPU costs only what a job uses of it. The contracts' instance table, its TypeScript mirror and the billing keeper's standard sandbox say the same sizes; the price scales, worked out as before from Cloudflare's list prices with every vCPU busy and the Durable Object behind each, are now 1.9 for g1t-2core and 3.4 for g1t-4core, against the larger standard machine, and the fallbacks for a sandbox second (33 millionths of a dollar with its vCPU busy) and a build second (16) follow it. A test holds wrangler.jsonc's sizes to the contracts', and another the scales to the list prices. The docs' machine tables, the larger machines' prices and the Cloudflare deploy guide say so.c10ee4bHistory
- ..
- 0001_init.sql
- 0002_reusable_workflows.sql
- 0003_settings_access.sql
- 0004_self_hosted_runners.sql
- 0005_actions_cache.sql
- 0006_artifacts.sql
- 0007_run_protection.sql
- 0008_actions_access.sql
- 0009_run_attempts.sql
- 0010_jobs_self_hosted_lower.sql
- 0011_schedule_rules.sql
- 0012_runner_task_runs.sql
- 0013_action_registry.sql
- 0014_managed_workflows.sql
- 0015_runner_isolation.sql
- 0016_log_chunks.sql
- 0017_workspace_managed_workflows.sql
- 0018_desktop_runners.sql
- 0019_brokered_secrets.sql
- 0020_job_token_rotation.sql
- 0021_log_retention.sql
- 0022_runner_machine.sql