Hi Enhance Support Team,
I am writing to request a feature that allows server administrators to disable or hide the manual "Create Database" option on a per-package basis.
The Use Case & Problem:
For our WordPress-specific plans, we strictly limit the "Website" quota to 1. However, to allow users to utilize the native Enhance Staging feature, we must set the "Databases" limit to 2.
Unfortunately, users are actively abusing this second database quota. Instead of using it for a staging environment, they manually create the second database and install a completely separate live site inside a subfolder (e.g., domain.com/secondsite).
Why Current Workarounds Fail:
- Setting DB limit to 1: This completely breaks the Enhance native staging feature.
- Custom CSS: Hiding the button via Custom CSS applies globally. We cannot do this because we need users on our Node.js and Laravel packages to freely create and manage their databases.
- Resource/Inode Choking: Relying on strict inode or PHP worker limits to prevent subfolder installations creates a poor user experience and increases our support ticket overhead.
Proposed Solution:
Please add a simple toggle in the Package Settings (e.g., "Allow manual database creation: Yes/No").
If set to "No", the user should not see the option to manually create a database in their portal, BUT the Enhance system should still be able to auto-provision that second database in the background when the user initiates the Staging creation process.
This would give hosting providers much better control over resource abuse while keeping the native staging functionality intact for specific packages.
Looking forward to your thoughts on implementing this.
Best regards.
Mahmud Sabuj
