ServerAvatarDocs
Applications

Blank PHP and static sites

The two types that install nothing — an empty PHP-ready site, and a directory of plain HTML served as files.

Two types exist for code the panel should not touch: it creates the system user, the directory, the web-server configuration and the certificate, puts a placeholder page there, and stops.

Blank PHP site

An empty site — upload your own files.

A site with its own PHP-FPM pool, ready for anything you put in it: a legacy application, a framework the catalog does not package, a single index.php.

Blank PHP site essentials: a PHP version picker and nothing else

The only question is the PHP version, because that is the only thing the panel has to decide for you. There is no version range — every installed version is offered.

Static site

Plain HTML, CSS and JavaScript.

No runtime at all. The web server hands out files from the directory, which makes it the fastest thing the panel can run and the one with the least to go wrong.

Static site essentials: no fields beyond Advanced settings

There is nothing to configure, so the section is empty apart from Advanced settings.

Static site advanced settings, holding only Web root

Web root

For both types this is the setting worth getting right. It is the directory inside the application that the web server serves, and it defaults to / — the application folder itself.

You haveSet web root to
index.php or index.html at the top level/
A framework with a public directory/public
A generated site under dist/ or build//dist, /build

It is editable afterwards from the application's dashboard, so a wrong guess is not permanent.

Getting your files onto the server

Creating the application gives you somewhere to put files. Three ways in, all covered elsewhere in this guide:

  • Files — the panel's own file browser, on the application.
  • SFTP or SSH — as the system user the application was created with, using the password set during creation.
  • Git — if the code is in a repository, deploy from Git instead and let the panel pull it.

Limits and caveats

  • A static site has no PHP. If you later need PHP, that is a different application type, not a setting.
  • The placeholder page is a real file in the web root. Delete or overwrite it when you upload your own.
  • Nothing is deployed automatically. These two types never fetch, build or run anything on your behalf.

On this page