Last updated 6th July 2022
Every application you deploy on Web PaaS is built as a virtual cluster, containing a set of containers. The default branch of your Git repository is always deployed as the production cluster. Any other branch can be deployed as a development cluster.
By default, you can have up to three live development clusters at once, but you can buy more on a per-project basis.
There are three types of containers within your cluster:
- one router
- one or more application containers
- zero or more service containers
All of those containers are managed by three special files in your Git repository:
In most cases, that means your repository looks like this:
yourproject/ .git/ .platform/ services.yaml routes.yaml .platform.app.yaml <your application files>
There is always exactly one router per cluster.
The router of a cluster is a single nginx process.
It's configured by the
It maps incoming requests to the appropriate application container
and provides basic caching of responses, if so configured.
It has no persistent storage.
Service containers are configured by the
There may be zero or more service containers in a cluster,
depending on the
For zero services, don't include the
services.yaml file in your repository.
The code for a service is provided by Web PaaS in a pre-built container image,
along with a default configuration.
Depending on the service,
it may also include user-provided configuration in the
Examples of services include MySQL/MariaDB, Redis, and RabbitMQ.
There always must be one application container in a cluster, but there may be more.
Each application container corresponds to a
.platform.app.yaml file in the repository.
If there are 3
.platform.app.yaml files, there are three application containers.
Application containers hold the code you provide via your Git repository.
Application containers are always built off of one of the Web PaaS-provided language-specific images,
Node.js 14, and
It 's also possible to have multiple application containers running different languages or versions.
For typical applications, there is only one
which is generally placed at the repository root.
Did you find this guide useful?
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.