Control Panel

digitalexpanse

Start building in best practices early on to help business owners moving forward. Starting with the control panel, that essentially manages internal operations and segment everything customer oriented.

segment internal operations from customer operations
install control panel to server dedicated to managing operations, disable installing anything other than operations and management services.
segment websites (internal)
control/dashboard related websites should be segmented from customer websites
DNS
If DNS is not installed, remove nameserver requirements on control panel, ideal for those using external services like Cloudflare, who'll never modify nameservers or at least until Cloudflare API sync is built into enhance.
Email
If email is disabled, remove roundcube.
Staging Domain
suffix added by customers, allow "staging" as valid entry and disable requirement for nameservers
create env that is friendly to Cloudflare, etc.
Server placement (Random, Least Load, Least Websites)
Allow manual selection. We place spec websites on spec servers for spec reasons.

Hope this makes sense, but overall best practices generally have positive impact for everyone!

Adam

Hi digitalexpanse,

You can do this. Once you have installed your control panel server, disable application and database roles on it and no customer websites will be placed there. Those roles must remain installed to support Roundcube and phpMyAdmin. Don't install email, DNS or backup roles on your control panel server. This is recommended for multi server clusters.
Can you elaborate how you would like them to be further segmented? phpMyAdmin and Roundcube are in their own PHP containers. The control panel website just serves the statically built UI and proxies the API to the API server. If you don't want to see them in the website list you can deselect "service websites" from the preferences icon (system cog) at the top right of the website listing.
If you have no nameserver domains configured, there should be no yellow "nag" warning in the client's dashboard about setting nameservers. The DNS configuration section is retained because we have a method for syncing to a 3rd party DNS system. This is described in our API spec but not yet exposed in the UI. Whenever a customer changes their zone, the full zone contents are pushed to the remote end point.
Good suggestion, we can do this. I've logged it as a feature request.
Can you elaborate on this? For staging websites the prefix is chosen by the customer rather than the suffix which is your staging domain set under platform settings.
When creating a website as the master organisation you can click "server placement" to manually specify the server on which the website will be provisioned. Customers and resellers cannot choose server placement themselves however you can also create dedicated subscriptions for customers which will place their websites on a particular server (dedicated to them). You can also create plans (for shared hosting) which will provision to a particular server group. For instance you could create "Pro Hosting USA" which provisions to your American servers only. If there are other options you would like to see, please let us know.

Kind regards,

Adam.

digitalexpanse

websites
customer, not customer, I believe answered through 1.
seems fine, entirely reliant on Cloudflare
you ask for staging, but require FQDN, simply accept "staging" as wildcard for all websites, applying to all customers
perfect, we'll never have resellers or customers selecting anything

standtech

As per the January 2024 roadmap, enhance control panel Migration would include individual website migration from one enhance to another ?

Adam

standtech As per the January 2024 roadmap, enhance control panel Migration would include individual website migration from one enhance to another ?

That's a different feature but it's coming very soon. You will be able to download a portable backup and import it to a different cluster in a similar way to the current cPanel/Plesk import functionality.

Obviously there is the usage case of running multiple clusters (or decommissioning a cluster and moving customers to a new one) but the primary reason for this feature is to make it easier for customers to move between hosting providers where both the losing provider and the gaining provider are using Enhance.