CWP 2.0.3 (Edge) – changes since 2.0.2
The Edge channel ships new features early. It also includes every fix from the
current LTS release (1.30.9 – see the LTS changelog). New in 2.0.3:
Features
CWP Cage (resource limits):
- CloudLinux-style per-account resource limits. Each hosting account can be given CPU (%), memory, process and I/O limits, enforced with Linux cgroups, and the account's PHP runs isolated through the CWP lsPHP handler (cwpsapi). Limits can be set per package (every account on the package inherits them) or overridden per account, and legacy cgroups settings are imported automatically. The Cage live view shows real per-account CPU/memory usage, busiest accounts first. (CWPpro)
lsPHP per domain (PHP Selector):
- When an account is enabled for lsPHP, its PHP Selector now offers an "lsPHP" option next to Default / Selector CGI / Selector FPM, so a single domain can be switched to the high-performance lsPHP handler on a chosen PHP version. The option appears only on CWPpro servers with the handler installed and the account enabled for it; every other account looks and works exactly as before.
Fixes
Migration (external panels):
- The DNS import no longer corrupts records: a record's type is no longer glued onto its value (A/CNAME/MX records imported cleanly), and long quoted TXT records (SPF, BIMI) are no longer truncated at the first semicolon. In addition, A/AAAA records that point at the old server's IP are now repointed to the new server — including wildcard and subdomain records — so mail and web for every subdomain land on the new server after a migration instead of the decommissioned one.
Cloudflare (user panel):
- Input hardening on the module entry point.
Plus all fixes from LTS 1.30.9.