The UI already speaks "bandwidth"; the internals still said "traffic" for the same concept (monthly quota, NIC counters, throttling). Align the whole stack: - db: table `traffic` -> `bandwidth`, column `traffic_quota_gb` -> `bandwidth_quota_gb` (fresh schema, no migration needed) - lx: `Traffic`/`TrafficMap` -> `Bandwidth`/`BandwidthMap` - mgr: `SampleTraffic`/`TrafficFor`/`EnforceTrafficLimits`/ `ParseTrafficGB`/`UpdateQuotasAndTraffic` -> bandwidth equivalents - panel/admin/main: template fields, form names, CLI flags and vars - docs and AGENTS.md updated; ordinary English uses of "traffic" (forwarded traffic, inter-container traffic) are kept 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, 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 |
| development.md | Building, testing, releasing, conventions |
See also AGENTS.md at the repo root — short version aimed at AI coding agents.