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:
- Projects: the smallest level of organization, these are your individual services such as a frontend app or database
- Sub-Groups: ex "production" or "staging", these can contain multiple projects. Two sub-groups in the same group can have different projects.
- Groups: the highest level of organization. These contain your sub-groups and projects.
It's not possible to have one level of organization without the higher levels. For example, you cannot have a project without a group or sub-group.
Here is a diagram showing the structure of an example project:
On the Dashboard, clicking on a project containing only a single project in every sub-group will automatically redirect to that app. You can manually view the group or sub-group 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 group and project name for you, in an sub-group 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 a sub-group
You can create environment variables that are scoped to all projects within a sub-group, through the sub-group 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 a sub-group called "production" and a group 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:
- Go the Dashboard and select an app
- Select "production" from the breadcrumb links at the top of the page
- Select the "Add Project" button on the right side of the page, and then move the other apps into this sub-group.
- To create another sub-group, for example "staging", select the project name from the breadcrumbs (the second link) and then click "New sub-group" 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 sub-groups. For example, in sub-group
europeyou may have a database, backend and frontend all hosted in a specific cloud & region.