Sites

Every site has its own space on the server, separated from the others: a problem on one site (for example a vulnerable plugin) cannot touch the files of other sites.

Creating a site

Open Sites and choose New site.
Type the domain, without http:// and without a path: for example example.com.
If you want, add aliases, other names that open the same site (for example www.example.com).
Choose the PHP version. You can leave the other fields (system user, document root) empty: the panel uses safe values.
Press Create site.

The site is ready in a few seconds. For visitors to see it, the domain must point to the server address: you set it in your registrar's panel (where you bought the domain), with a DNS record of type A.

Where to put the files

The public files of the site go in the public_html folder. You can upload them with the file manager or via SFTP.

Changing PHP version

Open the site: on the Overview tab you can change the PHP version. The change is immediate. The list shows the versions installed on the server and allowed by your package (see PHP versions).

PHP settings of the site

On the same tab, the PHP settings box sets the values of this site only:

Memory (memory_limit): from 32 to 1024 MB;
Uploads (upload_max_filesize): from 1 to 1024 MB (the form limit and the web server limit follow);
Maximum time (max_execution_time): from 10 to 600 seconds;
Form fields (max_input_vars): from 1000 to 100000;
Show PHP errors (display_errors): only while developing.

Leave a field empty to use the server default. The panel checks the new configuration before applying it and, if something goes wrong, keeps the previous one. The settings stay when you change PHP version.

Redirects, protected folders and other rules

In the Rules tab of the site you set 301/302 redirects, password-protected folders, IP blocker, hotlink protection, error pages and MIME types: see Site rules. The Statistics and Logs tabs show visits, traffic and the web server logs: see Logs and statistics.

Git deploy

In the Git tab of a PHP site you connect a repository: address (https://… when public, git@host:path when private), branch and folder of the site (usually public_html, which must be empty on the first deploy: the panel's welcome page is removed). Deploy fetches the branch as the site user; the following deploys bring the folder to the latest version of the branch, without touching the files that aren't in the repository (uploads, for example).

Deploy key: for a private repository create the key and add it to the repository as a read-only key.
Webhook: create the address and paste it into the repository's webhooks (push event): at every push the deploy starts by itself.
composer install after the deploy, when the repository has composer.json and Composer is installed on the server.

Node.js, Python and .NET applications have their own deploy in the Application tab.

Deleting a site

Open the site and press the bin. You can choose to keep the files on the server. Everything else (configuration, scheduled tasks, SFTP access, certificate) is removed.

Deletion cannot be undone. If in doubt, make a backup first.