Type

The selected type will determine the configuration of your website.

You can choose between basic types where you basically decide which technology stack should be provided (e.g. plain HTML vs. PHP) and configure additional things by yourself.

Or directly choose an application type which offers a blueprint of both the technology stack and an opinionated and tested base configuration for your product.

Independent of the chosen type, always create a new website via our Cockpit. It will serve as the “wrapper” and our automation will provision the needed bits depending on the configuration details of the website.

Basic Types

To run your own application with a certain technology stack, use one of our basic types.

Docker

This type is used to run your own Docker container behind a webserver acting as a reverse proxy.

  • Docker rootless will be installed and configured

    • containers are run in a isolated user namespace

    • user and group IDs within the container are mapped to non-existing IDs on the host

    • you only see the containers of your website user

  • a sample .htaccess file with directions to proxy incoming requests to your container is created

  • the port on which the proxy configuration expects your container to listen is also available as WEBSITE_PORT environment variable

Warning

To persist data in docker containers use volumes instead of bind mounts, due to permission conflicts. For more information see Persisting Data.

Tip

Take a look at our Getting Started with Docker How-To.

Tip

We know of certain setups where it is not possible to use rootless mode (e.g. Docker Swarm). If you encounter this problem, please contact us and we will check for a possible solution.

HTML

Used to create a HTML only or “static” website, without dynamic processing or application.

Furthermore, you can use this website type to configure any special needs in .htaccess, for example:

  • reverse proxy

  • redirects

Tip

If you have many domain names that you’d like to redirect with certificates and everything, maybe our Redirect Service could be of use for you.

Node.js

Your Node.js application is executed with a daemon controlled by systemd.

  • select the desired node version trough nvm

  • by default, the latest node lts version is installed

  • a sample .htaccess file with directions to proxy incoming requests to your Node application is created

  • the port on which the proxy configuration expects your application to listen is also available as WEBSITE_PORT environment variable

  • symlink your application’s app.js to ~/app.js or overwrite path or other daemon options at OPTIONS in ~/cnf/nodejs-daemon.conf:

    OPTIONS="/home/<website-name>/application/app.js --prod"

Tip

Take a look at our Getting Started with Nuxt.js How-To.

PHP

  • PHP in the selected version installed, running and configured

  • you can set custom PHP configurations trough the ~/cnf/php.ini file

  • see the PHP Documentation for details.

Tip

Reload PHP by using the php-reload shortcut, or use php-restart to fully restart the PHP pool.

Warning

PHP 7.4 (EOL), PHP 8.0 (EOL) and PHP 8.1 (EOL) do no longer include Intl, as they are no longer compatible anymore.

Application Types

We provide elaborated types for certain web applications. If your desired application is amongst them, we recommend to use them instead of a basic type.

Drupal

Neos

Tip

Take a look at our Getting Started with Neos How-To.

TYPO3 v11

TYPO3 v12

TYPO3 v13

Tip

Take a look at our Getting Started with TYPO3 How-To.

Wordpress

Tip

Please disable the built in HTTP call to wp-cron.php by setting define('DISABLE_WP_CRON', true);. This additional call is not necessary and disabling it will lower the load on your system.

Tip

Take a look at our Getting Started with WordPress How-To.