Skip to main content

Organizing your Zeet Apps

Note: This document refers to changes made to the platform in August 2022. For details about the migration, see Migrating.

How it works

Zeet has three components to help group related apps and configurations:

  • Apps: the smallest level of organization, these are your individual services such as a frontend app or database
  • Environments: ex "production" or "staging", these can contain multiple apps. Two environments in the same project can have different apps.
  • Projects: the highest level of organization. These contain your environments and apps.

It's not possible to have one level of organization without the higher levels. For example, you cannot have an app without an environment or project.

Here is a diagram showing the structure of an example project:

On the Dashboard, clicking on a project containing only a single app in every environment will automatically redirect to that app. You can manually view the project or environment by clicking on one of the breadcrumb links at the top of the app view.

Creating a new project

You can create a new project when creating a new app, using the Project Settings tile in step 4. By default, Zeet will create a new project and app name for you, in an environment called production. All of these values can be changed by clicking the tile's edit button on the top right.

Applying environment variables to all apps within an environment

You can create environment variables that are scoped to all apps within an environment, through the environment settings page:

Migrating from the previous system

Make sure to read How it Works first

Prior to August 2022, Zeet only had projects, which are now referred to as apps. All customers have been automatically migrated from this system. For example: If you had a legacy project called "my-frontend", a new app would be created with the same name, within an environment called "production" and a project called "my-frontend".

The automatic migration does not know how your apps should be structured, so we suggest manually organizing your apps to better reflect this. For example: If you have migrated projects called "frontend", "backend" and "database", you can merge those into a single project with the following steps:

  1. Go the Dashboard and select an app
  2. Select "production" from the breadcrumb links at the top of the page
  3. Select the "Add App" button on the right side of the page, and then move the other apps into this environment.
  4. To create another environment, for example "staging", select the project name from the breadcrumbs (the second link) and then click "New environment" and check "Copy existing apps".

Other use cases

  • Region specific apps: if you require different instances of your app and its supporting services for specific regions, you can have region-specific environments. For example, in environment europe you may have a database, backend and frontend all hosted in a specific cloud & region.