bluebluesodaandCommandCodeBot
3b8cfdcd93
- `snapshots.share` and `cpu_limit.*` are now config.yaml fields managed with `vps config set` (validated, shown by `vps config list/help`) instead of being panel/DB-only settings; the admin panel now shows the CPU rule read-only and the snapshot-sharing card is gone - both apply immediately: `vps config set` writes the config file, mirrors the value into the DB and applies it right away — no panel restart — the same pattern as net.v4_forward. `vps install` refreshes the mirror from the file - the CPU rule is read from the mirror (falling back to the config file) so the enforcer and the read-only card pick up a change live; the share toggle too - drop the now-unused admin routes/handlers, the DB-only rule setting and the ConfigSet CPU form Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Documentation
Technical documentation for vpsmgr. All docs are in English.
| Doc | What it covers |
|---|---|
| architecture.md | System design: components, storage, network, security, traffic, users and user groups, image, install/uninstall lifecycle |
| configuration.md | Full reference for /etc/vpsmgr/config.yaml |
| ipv6.md | IPv6 pass-through design: deterministic addresses, prefix support, routing, installer flow |
| ipv6-ndp-responder.md | Why prefix mode replaced ndppd with an in-tree NDP responder, design hardening, and what to test at scale |
| development.md | Building, testing, releasing, conventions |
See also AGENTS.md at the repo root — short version aimed at AI coding agents.