Applications¶

Overview¶

An application in Wodby is built on a stack and can contain multiple instances. Each instance is a deployed copy of the app assigned to an environment. Environments are named objects with a fixed type such as prod, staging, or dev. Creating a new application automatically generates its first instance.

Every app can have an unlimited number of instances but at least one
You can deploy as many instances as you want
You can deploy instances of the same app across different Kubernetes clusters, including self-hosted K3S clusters on different servers
One stack per application
Different instances can have different revisions of the same stack

flowchart TD
    subgraph App2["<div style='margin-top:10px; white-space: nowrap;'>Your app</div>"]
        subgraph group[ ]
            Dev["Dev instance"]
            Staging["Staging instance"]
            Prod["Production Instance"]
        end
        style group fill:none,stroke:none,stroke-width:0px
    end   

    subgraph Stack["<div style='margin-top:10px; margin-right: 60px; white-space: nowrap;'>App stack</div>"]
        subgraph group3[ ]
            Rev1["Revision #1"]
            Rev2["Revision #2"]
        end
        style group3 fill:none,stroke:none,stroke-width:0px            
    end

    Dev --> Rev1
    Staging --> Rev2
    Prod --> Rev2

Use this section to create apps, understand how apps, instances, and app services relate, and deploy the same app across multiple environments.

Quick model¶

Object	What it means
App	The top-level application record
App instance	One deployed copy of that app, assigned to an Env
App service	One service inside one app instance

See App vs app instance vs app service for the fuller explanation.

Creating New Application¶

There are 5 steps of creating a new application:

Step 1¶

Select the app Owner.
Choose Organization <organization> to create an organization-owned app.
Choose Project <project> to create a project-owned app.
Select a stack
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¶

Select where you want to run the first instance of your application. The form offers two destinations:

My clusters
Choose one of your existing clusters
This can be a managed Kubernetes cluster created from a cloud integration
It can also be a self-hosted K3S cluster connected from Kubernetes > Connect server
Wodby Cloud
Wodby creates and manages a new cluster for this application
For persistent Wodby Cloud clusters you choose region, CPU type, machine type, and minimum and maximum node counts
Persistent Wodby Cloud clusters require a paid plan
For testing, enable Demo to create a free temporary Wodby Cloud cluster that is deleted automatically after 24 hours together with its applications

Step 3¶

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 is *.[instance-name].[app-name].[org-name].wodby.app. This root domain is used to generate technical domains for services that expose HTTP ports

Step 4¶

Build sources¶

For buildable services select a build source. A build source is a git repository that contains your application code and, usually, CI pipeline manifests. Services often provide a public template that you can use directly or clone. You can also use your own git repository.

Settings¶

Configure settings for services that provide them.

Volumes¶

Specify sizes for persistent volumes. Some services, such as Redis, may provide optional volumes. For those, specifying size 0 means no persistent storage will be created.

Integrations¶

Select integrations. If a service does not provide a dedicated integration, you can still attach a variable integration to a non-external service.

Databases¶

For database services you can optionally select an existing database server. By default, Wodby will create a new database server for you.

Imports¶

Specify imports. For services that provide import functionality, such as database services, you can upload an archive or specify a public URL to import from.

Step 5¶

Review your application configuration and click Create new app.