Environment Lifecycle
In order to fully understand how the Artifakt platform works, it is essential to have a good understanding of the life cycle associated with the environment.

Environment and Criticality

When you create an environment, you will need to define its criticality. Usually, our users define their production environments as critical (business-critical applications) and their testing and development environments as noncritical (non-business critical applications).
Depending on your choice, some features will become available for that specific environment.
Environment monitoring (health check)
Highly available database
Retention of database backups
1 day
7 days
24/7 support for production incidents
​Burstable performance instance
Criticality also affects the cost of an environment. As a consequence, adding up advanced features on a critical environment will lead to an additional cost that should not be overlooked.

Creating an Environment

To create an environment, go to the desired project and click on New Environment.
Creating a new environment
You must then define some important information:
When you create an environment, it has the status Offline. The environment does exist in the Artifakt Console but is not yet deployed and available online. At this stage, no Cloud resources have been created yet.
To make the environment accessible online, you need to start building the cloud platform. To do this, go to the desired project and click Build in the drop-down menu of the desired environment.
Building an environment
The status of this environment then changes to Building, which means that the cloud resources of the platform are being created.
Please note that when building the environment, a first code deployment is automatically performed.
Building time varies according to the selected platform type:
  • Starter – approx. 5 min
  • Scalable – between 35 and 45 min
When the construction is successfully completed, the status of the environment will change to Online, which means that the Cloud platform has been successfully created. You will then have to deploy the application source code when you are ready.

Duplicating an Environment

Duplicating an environment allows you to quickly create a copy of an existing environment and keep the same settings.
When duplicating, you can adjust a few settings including:
  • The environment name (must be unique within the same project)
  • The Git branch to use for code deployment
  • The Custom configuration (JSON)
If you duplicate an environment already deployed online (with Online status), the copy will not be deployed until you start building it. In other words, a duplicated environment is always Offline by default.

Deleting an Environment

When an environment is Online, you can destroy it by clicking Destroy in the drop-down menu of the desired environment. The Cloud platform associated with the environment will then be destroyed and the environment will return to Offline.
Destroying an environment
At this point, you can then completely delete the environment from the Artifakt Console by clicking Delete in the drop-down menu of the desired environment.
Deleting an environment
The difference between destruction and deletion exists for practical reasons. You can destroy an environment today and rebuild it the next day without having to re-create it entirely in Artifakt or configure it again according to your needs.

List of Statuses of an Environment

The status of an environment reflects the state of the associated underlying Cloud platform (the infrastructure) and not the state of your application. For example, you may encounter a situation where the status of the environment is Online, because the Cloud platform is working properly, while your application is not working and remains inaccessible (for various reasons, misconfiguration, bug or other).
Please find below the statuses an environment can go through.
The platform is not deployed online (no Cloud resource created).
The platform is under construction (Cloud resources are being created).
The platform is being updated (changing sizing, adding / removing services, etc.).
The platform is deployed online (Cloud resources have been created).
The platform is being destroyed (Cloud resources are being deleted).
An error has occurred on the platform. Please contact our Support team.
Last modified 1mo ago