g1t/services/billing/migrations/0021_no_quotas.sql

23 lines1,377 bytesCodeBlame

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas1-- No per-feature quotas on the plan. A workspace on the plan pays for what
2-- it uses, from the first unit, at cost plus the margin, drawn from its
3-- included usage first; nothing but its spend limit stops it. The forge
4-- is free for everyone up to the same amounts (1 GB of private storage,
5-- 50,000 git operations a month); past them, the plan pays and a free
6-- workspace is held to them. Projects, previews and the apps behind them
7-- are not metered at all. See src/features.rs and src/storage.rs.
8
9-- How much of a pending source there was, for the Billing page's
10-- "This month's usage": `1.2 million requests and 3.4 million CPU ms`.
11ALTER TABLE pending_usage ADD COLUMN detail TEXT;
12
13-- Apps are not metered: Workers for Platforms includes far more scripts
14-- than g1t runs, so an app costs g1t only its requests and CPU.
15DELETE FROM prices WHERE meter = 'app_month';
16
17-- Meters whose titles said "past the plan": every unit is metered now.
18UPDATE prices SET title = 'Custom domains' WHERE meter = 'custom_domain_month';
19UPDATE prices SET title = 'Private repository storage past the free 1 GB' WHERE meter = 'private_storage';
20UPDATE prices SET title = 'Git operations past the free 50,000 a month' WHERE meter = 'git_operations';
21
22-- allowance_use rows of kind build_seconds stay: they are now a plain
23-- count of the month's build seconds, all of them charged.