Skip to content

Projects and environments ​

Projects ​

A project groups the applications and databases of one product. Each project starts with a production environment and can have staging and development too.

  • Each environment is separate: its own services, variables, databases and addresses. An application only reaches the databases of its own environment.

  • On the server, each environment is a Kubernetes namespace named orbit-<project>-<environment>, with the name the project was created with:

    sh
    sudo k3s kubectl -n orbit-<project>-production get deploy,pods,ingress,certificates

Changing and deleting ​

A project's Settings, next to its environments:

  • Name, description and color. A new name must not be one another project uses or used. What already runs keeps its namespace and addresses; only services added later take the new name in their generated address.
  • Removing staging or development. Everything in it stops and is removed with its data, and previews that copied it are turned off. Production stays while the project exists.
  • Deleting the project. Every environment, preview, application and database goes, with their data.
  • Deleting an application is at the bottom of its Settings. A database has the same section on its page and is refused while an application still references it: disconnect it first.

Every removal asks you to type the name. Backup files are kept: local ones under /var/lib/orbit/backups/<database id>, external ones in their bucket.

Workspaces ​

  • What belongs to a workspace: projects (with their environments, services, databases and backups), the GitHub connection, registry credentials, backup storages and activity. Servers are shared by every workspace.
  • Switching: the switcher at the top of the sidebar. Each browser remembers the last one it used, and opening a link to a project in another workspace switches to it.
  • GitHub per workspace: each workspace connects its own account or organization, so a "Personal" workspace can read your account while a "Cortex Labs" one reads the organization.
  • Names: project names are unique across the whole Orbit, because they name the Kubernetes namespace and the generated address.
  • Creating and renaming: in Settings → Workspace.

Orbit by Cortex Labs