Each environment in Stormkit has a configuration which is divided into two sections. The first section is the environment configuration, where you can provide the name of the environment, the branch it points to and whether auto publish is enabled or not.
|Environment name||The name of the environment. Each application can have as many environments as needed. You cannot reuse the same environment name in a given application.|
|Branch||Every environment is assigned a branch. When auto deployments are enabled, the commit will be built using the matching environment's configuration. If there is no environment matching for that branch, the default environment's configuration will be used.|
|Auto publish||When enabled, successfull deployments will be automatically published. When a deployment is published, the domain will point to that deployment.|
The second section is regarding the build configuration. When building
and deploying an application, these configuration settings will be used.
Stormkit has a built-in support for the following frameworks:
Nest.js. This built-in support allows you to toggle
Serverless or Static mode with a switch under your Environment
configuration. We'll understand your
directly from the framework configuration file.
If any other framework is used or no framework is used at all, the build
configuration will display two additional fields:
|Server file||This is required only for hybrid applications. It points the entry file for the server side application. Stormkit will reuse the webpack configuration of the client side, make adjustments to it, and wrap this file with some additional logic to prepare it for the serverless environment. Therefore, this file is expected to export a function. More information here.|
The publish folder will be uploaded to our CDN. This folder is
expected to have an |
The build command to execute. You can chain multiple commands with
the logical and (|
|Environment variables||The environment variables that will be injected during build time.|