nexxo 98d884727a Warn that a package cannot be placed, before somebody pays for it ... The platform books thick: a package reserves its whole disk_gb — the sold quota plus the machine's own overhead — on ONE host at placement. That is the right choice for a small operator, because nothing can quietly overfill. It has one consequence nobody was being told about: the catalogue goes on offering a package no host has room for, and the first anyone hears of it is a PAID order failing at the reservation step. On the machine this was found on the numbers are stark. 2 x 512 GB NVMe in a mirror is about 400 GB usable; Start reserves 120, Team 540, Business 1050, Enterprise 2100. Three of the four packages on sale cannot be placed at all, and the fourth fits three times. So the console says so now, per package, with the shortfall — "Team needs 540 GB, the roomiest host has 260" — because "buy a server" is not the decision. "Buy a server big enough for what I am selling" is. Two things it deliberately does not do. It does not warn on an installation with no host at all: that is a machine nobody has onboarded yet, it has its own notice, and without the guard a fresh console greeted its operator with one warning per package before they had done anything. And it does not take the overview down when the catalogue cannot be read — a capacity warning does not get to break the page somebody opens when something is already wrong. The largest FREE HOST, never the sum: an instance goes on one machine, so two hosts with 300 GB each cannot take a 540 GB package between them. And when placement does fail, the log now names the shortfall instead of only 'no_capacity'. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-07-29 18:20:51 +02:00
..
Billing	Book a downgrade for a date that cannot move, and sell a module once	2026-07-29 17:51:37 +02:00
Deployment	Update on a schedule if the owner wants one, and say where incidents go	2026-07-29 15:01:54 +02:00
Devices	Show where an account is signed in, and let it sign the other places out	2026-07-28 23:38:17 +02:00
Dns	Add the SSH identity to the vault, and give deployment config a console page	2026-07-29 00:52:44 +02:00
Domains	Prove a custom domain before serving it, and keep proving it	2026-07-29 14:47:51 +02:00
Env	Add a raw .env editor to the Integrations page, with a net under it	2026-07-29 01:51:27 +02:00
Mail	Bound the mail test-send and real send to a timeout instead of hanging	2026-07-28 16:36:14 +02:00
Maintenance	Keep the purpose mailer through the queue instead of losing it to the default	2026-07-28 03:50:02 +02:00
Monitoring	Add the SSH identity to the vault, and give deployment config a console page	2026-07-29 00:52:44 +02:00
Provisioning	Warn that a package cannot be placed, before somebody pays for it	2026-07-29 18:20:51 +02:00
Proxmox	Apply a bought plan change instead of only pricing it	2026-07-29 17:18:55 +02:00
Secrets	Add a raw .env editor to the Integrations page, with a net under it	2026-07-29 01:51:27 +02:00
Ssh	Add the SSH identity to the vault, and give deployment config a console page	2026-07-29 00:52:44 +02:00
Status	Let an incident be deleted, and start measuring whether the hosts answer	2026-07-29 15:16:48 +02:00
Stripe	Manage the Stripe key from the console, behind a password and a test	2026-07-27 09:01:16 +02:00
Traefik	Serve the custom domain, not just announce it	2026-07-29 16:44:52 +02:00
Traffic	feat(billing): the plan catalogue becomes three tables, and config stops selling	2026-07-26 12:05:56 +02:00
Wireguard	Add the SSH identity to the vault, and give deployment config a console page	2026-07-29 00:52:44 +02:00