Domain-Based Folder Naming

Shaijee

Hello, Currently Enhance CP creates folders in /var/www with a long UUID (for example: 0d3ab650-ba90-98a0-afrw-6ca3956ec47f). That works, but it’s hard to identify which folder belongs to which domain without opening each one.

Suggestion: Create site folders using the domain name instead of a UUID. For example:

/var/www/example.com
/var/www/example.org
/var/www/client-site.net

Benefits:

Easy identification — instantly see which folder is for which domain.
Faster management — quicker when using SSH or SFTP.
Better organization — less confusion with multiple sites.

Optional: If duplicate names are possible, append a short unique ID after the domain, for example:
/var/www/example.com-1234

This change would make the workflow more user-friendly without affecting functionality.

Thank you for considering this improvement.

cPFence

Shaijee Suggestion: Create site folders using the domain name instead of a UUID.

It’s probably going to be difficult to replace the UUID structure since many Enhance features depend on it, meaning it would require significant internal changes. A simpler and safer approach would be to add and maintain symlinks.

That’s what we do in cPFence - as an optional feature that can be enabled - by creating cPanel-style folder names and keeping them in sync when accounts are added or deleted. The Enhance team could implement something similar without major rewrites, giving you human-readable paths while still keeping the UUIDs for system operations.

8Dweb

Shaijee

cPFence It’s probably going to be difficult to replace the UUID structure since many Enhance features depend on it, meaning it would require significant internal changes. A simpler and safer approach would be to add and maintain symlinks.

That's complex, but when v12 was rewritten we (users) should have told them, or they should have named the domain-based folder.

Clients only value UX above all.