<\/span><\/h3>\n\n\n\nTo add a hosting package:<\/strong><\/p>\n\n\n\n\n- Open Settings<\/strong> in the left side bar<\/li>\n\n\n\n
- Click Packages<\/strong><\/li>\n\n\n\n
- When the page loads click Add package<\/strong><\/li>\n\n\n\n
- Complete the form and select Add package<\/strong> to finish<\/li>\n<\/ol>\n\n\n\n
TIP<\/p>\n\n\n\n
The 'Duplicate package' tool allows you to make a carbon copy of an existing hosting package<\/p>\n\n\n\n
<\/span>Package settings explained<\/span><\/h3>\n\n\n\n<\/span>Details<\/span><\/h4>\n\n\n\n\n- Package name<\/strong><\/li>\n\n\n\n
- Package type<\/strong><\/li>\n<\/ul>\n\n\n\n
<\/span>Website resources<\/span><\/h4>\n\n\n\n\n- Number of websites<\/strong><\/li>\n\n\n\n
- Number of staging sites<\/strong><\/li>\n\n\n\n
- Disk space allowance<\/strong><\/li>\n\n\n\n
- Bandwidth allowance<\/strong><\/li>\n\n\n\n
- Number of MySQL databases<\/strong><\/li>\n<\/ul>\n\n\n\n
<\/span>System resources<\/span><\/h4>\n\n\n\nAll system resource limits apply per website. Any 'Addon domains' created under a single website will run within the same container\/namespace and will therefore be limited in aggregate to the per-website resource limits set. Staging websites have their own hard resource limits.<\/p>\n\n\n\n
By default a website is bound by the system resource limits of the package it is hosted on. It is possible for the Master Organisation and a Reseller to\u00a0override these settings on a per website basis.<\/p>\n\n\n\n
\n- Memory limit<\/strong> this is the total system memory which the website processes can consume. If this limit is reached, processes belonging to the website might be killed using the kernel's OOM killer. Usually the newest process will be killed first.<\/li>\n\n\n\n
- Virtual CPUs<\/strong> 1 \"virtual CPU\" is the equivalent of 1 core or CPU thread running at 100%. If this limit is reached, processes will be artificially slowed by the kernel to keep the CPU usage under the threshold.<\/li>\n<\/ul>\n\n\n\n
You can assign virtual CPU resources in smaller increments, for example you can assign 1.5 vCPUs to a website.<\/p>\n\n\n\n
WARNING<\/p>\n\n\n\n
Be wary of setting this limit too low. If website processes take longer to execute, more PHP workers will exist concurrently for a given traffic level and this will in turn consume more memory. It might be more efficient to assign additional CPU resources to your customers to save memory.:: warning<\/p>\n\n\n\n
\n- IOPS<\/strong> this is the number of disk operations per second that the website's processes can perform on any disk on your system. Your server's disks will have an inherent limitation to the number of IOPS they can process and setting a per-website limit helps prevent the storage from being overwhelmed by a single busy or malicious website.<\/li>\n<\/ul>\n\n\n\n
Bear in mind that a single PHP request could perform hundreds of IO operations - reading include files, session files, etc.<\/p>\n\n\n\n
If this limit is reached, the website's processes will hang in D state and will continue to consume memory. Be wary of setting this limit too low.<\/p>\n\n\n\n
\n- IO Bandwidth<\/strong> This is the amount of data which can be read or written by your website to and from the disks on your system. It functions similarly to the IOPS limit and processes reaching this limit will hang in D state until more IO bandwidth is available to them.<\/li>\n<\/ul>\n\n\n\n
TIP<\/p>\n\n\n\n
We recommend being generous with this limit, otherwise a single large file read performed by the website could cause the website to hit its limit.<\/p>\n\n\n\n
\n- Nproc<\/strong> This is the total number of processes the website can have within its container - including PHP workers, anything forked from PHP, cron jobs, SSH, etc. If this limit is reached then the website will not be able to fork additional processes.<\/li>\n<\/ul>\n\n\n\n
This might cause the 500 HTTP error code on the website.<\/p>\n\n\n\n
You should set this limit at least +5 higher than the PHP worker limit. For php-fpm this is configurable through the website's php-fpm settings in the UI. For LSPHP this is currently set to 50 and is not yet configurable.<\/p>\n\n\n\n
<\/span>Applications<\/span><\/h4>\n\n\n\n\n- Allow software installer<\/strong><\/li>\n\n\n\n
- Pre-install applications<\/strong>TIPWe recommend setting this to 'WordPress' to offer a WordPress specific package<\/li>\n\n\n\n
- Pre-install plugins<\/strong><\/li>\n\n\n\n
- Allow wp admin<\/strong><\/li>\n\n\n\n
- Allow WordPress manager<\/strong><\/li>\n<\/ul>\n\n\n\n
<\/span>Emails<\/span><\/h4>\n\n\n\nTIP<\/p>\n\n\n\n
If the Email section is locked, ensure an Email role installed on your Enhance cluster. You will not be able to offer the Email tools until an Email role is installed.<\/p>\n\n\n\n
\n- Number of Mailboxes<\/strong><\/li>\n\n\n\n
- Mailbox type<\/strong><\/li>\n\n\n\n
- Maximum dynamic mailbox size<\/strong><\/li>\n\n\n\n
- Number of forwarders only<\/strong><\/li>\n<\/ul>\n\n\n\n
<\/span>Domains<\/span><\/h4>\n\n\n\n\n- Number of domain aliases<\/strong><\/li>\n\n\n\n
- Allow DNS zone editor<\/strong><\/li>\n\n\n\n
- Allow Gmail DNS auto configuration<\/strong><\/li>\n<\/ul>\n\n\n\n
<\/span>Backups<\/span><\/h4>\n\n\n\nTIP<\/p>\n\n\n\n
If the Backup section is locked, ensure a Backup role installed on your Enhance cluster. You will not be able to offer the backup tools until a Backup role is installed.<\/p>\n\n\n\n
\n- Allow backups<\/strong> will give customers the option to view 'system' generated backups from within their account via the 'Backups' tab on websites dashboard. System generated backups will run according to your configured backup role settings.<\/li>\n\n\n\n
- Allow manual backups<\/strong> will allow customers to generate on demand backups via the 'Backup now' button in the 'Backups' tab on a websites dashboard.<\/li>\n\n\n\n
- Allow self restore backups<\/strong><\/li>\n<\/ul>\n\n\n\n
<\/span>Features<\/span><\/h4>\n\n\n\n\n- Allow self installation of SSL certificates<\/strong><\/li>\n\n\n\n
- Allow Let's Encrypt auto-provision<\/strong><\/li>\n\n\n\n
- Allow SSH keys<\/strong><\/li>\n\n\n\n
- Allow website cloning<\/strong><\/li>\n\n\n\n
- Allow php.ini editor<\/strong><\/li>\n<\/ul>\n\n\n\n
<\/span>Edit a package<\/span><\/h3>\n\n\n\nThe resources and features assigned to a packages can be edited after creation. Any changes made to an existing package will apply to new subscribers only.<\/p>\n\n\n\n
<\/span>Subscribe a customer to a package<\/span><\/h3>\n\n\n\nCustomers can be subscribed to multiple shared and dedicated packages and 1 reseller package which can all be managed from within the Enhance control panel.<\/p>\n\n\n\n
To subscribe a customer to a package:<\/strong><\/p>\n\n\n\n\n- Open Customer<\/strong> in the left side bar<\/li>\n\n\n\n
- Click on the customer you would like to subscribe a customer to<\/li>\n\n\n\n
- Visit the Packages<\/strong> tab<\/li>\n\n\n\n
- Select Susbscribe package<\/strong><\/li>\n\n\n\n
- When the modal loads, select the package and click Subscribe<\/strong> to finish<\/li>\n<\/ol>\n\n\n\n
<\/span>Upgrade or downgrade a package<\/span><\/h3>\n\n\n\nIt is possible to adjust the packages a customer is subscribed to. For example, if a customer's site grows in popularity you can seamlessly upgrade a customer from a shared hosting package to a dedicated package from within the Enhance panel.<\/p>\n\n\n\n
To upgrade or downgrade a package:<\/strong><\/p>\n\n\n\n\n- Open Customer<\/strong> in the left side bar<\/li>\n\n\n\n
- Click on the customer you would like to upgrade or downgrade<\/li>\n\n\n\n
- Visit the Packages<\/strong> tab<\/li>\n\n\n\n
- Select the drop down menu on the package you would like to upgrade or downgrade and click Upgrade\/downgrade<\/strong><\/li>\n\n\n\n
- When the modal loads, select the new package and click Subscribe<\/strong> to finish<\/li>\n<\/ol>\n","protected":false},"featured_media":0,"parent":56,"menu_order":3,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"_links":{"self":[{"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/docs\/82"}],"collection":[{"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/comments?post=82"}],"version-history":[{"count":1,"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/docs\/82\/revisions"}],"predecessor-version":[{"id":83,"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/docs\/82\/revisions\/83"}],"up":[{"embeddable":true,"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/docs\/56"}],"prev":[{"title":"Branding Settings","link":"https:\/\/sitebuilder.live\/docs\/resellers\/branding-settings\/","href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/docs\/80"}],"wp:attachment":[{"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/media?parent=82"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/sitebuilder.live\/wp-json\/wp\/v2\/doc_tag?post=82"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}