Skip to content

CLOS-4108: Rename 'Website isolation' to 'CloudLinux Isolates' in CLI output code examples#313

Merged
bogdanssh merged 1 commit intocloudlinux:masterfrom
IvanZhmud:clos-4108-cli-output-renaming
Apr 6, 2026
Merged

CLOS-4108: Rename 'Website isolation' to 'CloudLinux Isolates' in CLI output code examples#313
bogdanssh merged 1 commit intocloudlinux:masterfrom
IvanZhmud:clos-4108-cli-output-renaming

Conversation

@IvanZhmud
Copy link
Copy Markdown
Contributor

Summary

Renames all remaining "Website isolation" strings to "CloudLinux Isolates" in CLI output code example blocks and troubleshooting section headings in the CloudLinux Isolates documentation (docs/cloudlinuxos/isolates/README.md).

This is a follow-up to the prose/heading renaming PR that was merged on 2026-04-02. The current PR addresses the CLI output strings that were intentionally left unchanged in the first PR because they document actual cagefsctl output.

JIRA: CLOS-4108

Changes (17 instances)

# Context Old Output New Output
1 --site-isolation-allow-all example Website isolation was allowed for all users. CloudLinux Isolates was allowed for all users.
2 --site-isolation-deny-all example Website isolation was denied for all users. CloudLinux Isolates was denied for all users.
3-4 --site-isolation-allow examples Website isolation was allowed for user(s): ... CloudLinux Isolates was allowed for user(s): ...
5 --site-isolation-deny example Website isolation was denied for user(s): john CloudLinux Isolates was denied for user(s): john
6 --site-isolation-toggle-mode example Website isolation user mode toggled to 'deny_all'. CloudLinux Isolates user mode toggled to 'deny_all'.
7-8 --site-isolation-enable examples Website isolation was enabled for domain(s), ... CloudLinux Isolates was enabled for domain(s), ...
9 --site-isolation-disable example Website isolation was disabled for domain(s), ... CloudLinux Isolates was disabled for domain(s), ...
10-12 --site-isolation-list examples Domains with enabled website isolation for user ... Domains with enabled CloudLinux Isolates for user ...
13 --site-isolation-list (empty) No users with enabled Website isolation No users with enabled CloudLinux Isolates
14 --site-isolation-regenerate example Regenerated configuration website isolation for users: Regenerated configuration CloudLinux Isolates for users:
15 Troubleshooting heading "Website isolation is not enabled" "CloudLinux Isolates is not enabled"
16 Troubleshooting heading "Website isolation feature is not available on this platform" "CloudLinux Isolates feature is not available on this platform"
17 Troubleshooting heading "Website isolation is not allowed for user <username>" "CloudLinux Isolates is not allowed for user <username>"

Notes

  • CLI flag names (--site-isolation-*) are intentionally preserved for backward compatibility
  • This PR is blocked by CLOS-4109 (the actual cagefsctl utility update) — the docs should only be merged after the utility outputs are updated
  • Audit report: Slite document

… output code examples and troubleshooting headings

Updates all CLI output strings in code example blocks and
troubleshooting section titles to use the new product name
'CloudLinux Isolates' instead of 'Website isolation'.

17 instances changed across:
- Server-wide management examples (allow-all, deny-all)
- Per-user management examples (allow, deny, toggle-mode)
- Domain-level management examples (enable, disable)
- Monitoring examples (list, regenerate)
- Troubleshooting error message headings

Note: CLI flag names (--site-isolation-*) are intentionally
preserved for backward compatibility.
@bogdanssh bogdanssh merged commit d7c2833 into cloudlinux:master Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants