Applications¶

Overview¶

Application in Wodby consists of multiple instances that represent different environments: production, staging, development. When you create a new application you always create the first instance of that application.

Every app can have an unlimited number of instances but at least one
You can deploy as many instances as you want
You can also deploy instances of the same applications across different clusters
One stack per application
Different instances can have different revisions of the same stack

Creating New Application¶

There are 4 steps of creating a new application:

Step 1¶

Select a project where you want to place your new application
Select a stack
Select a kubernetes cluster where you'd like to deploy the first instance of your application
Optionally, if the stack has buildable services:
choose your CI system (Wodby CI by default)
choose your container registry (Wodby registry by default)
In the selected stack you can:
select a version (option) of a service
enable/disable optional services and change their configuration
configure resources request and limitation
configure autoscaling for scalable services

Step 2¶

Enter the name of your application and your instance. Application and instance names are used to generate machine names. Machine names are permanent and cannot be changed
Select the environment (Development by default)
Optionally, edit the root domain. By default, it's *.[instance-name].[app-name].[org-name].wodby.app. Root domain used to generate technical domains for services that provide http ports

Step 3¶

Build sources¶

For buildable services select a build source. Build source is a git repository that contains a build pipeline manifests. Usually, services provide a public template, that you can either use directly or clone it. You can also use your own git repository

Settings¶

Configure settings for service that provide such

Volumes¶

Specify sizes for persistent volumes. Some services, like Redis, may provide optional volumes, for those specifying 0 size would mean there will be no persistent storage

Integrations¶

Select integrations. If a service does not provide specific integrations, you can always add a variable integration for non-external services

Databases¶

For Database services you can optionally select an existing database server. By default, a new database server will be created for you

Imports¶

Specify imports. For services that provide import function (e.g. Database service), you can upload an archive or specify a public URL to import from

Step 4¶

Review your application configuration and click Create new app.