An environment is owned by a single user, and each user can have multiple environments.
We recommend having an environment per specific project a developer is working on. This helps promote the "development environment as code" paradigm throughout the organization by requiring a project team to define what language version and utilities they need in order to work on a project.
An environment can be created from the
Environments page in the dashboard. Select the
button and fill out the fields to create your new environment. You can name the environment anything
you like, but we recommend naming it after the project you're going to develop within it. Each environment belongs
to a specific team so that organizations can quota resource usage across a team, so you'll need to select
a team that the environment should be created underneath. The image is the base that the environment will
be created from and will contain all of the languages, tools, and utilities you need to work on a project.
/home folder persists and is outside the control of the image.
Feel free to load up the home with special settings, tools, extensions, projects, and whatever else you desire.
The home lives on a persistent volume, providing redundancy and fault tolerance to the most important files.
In order to add your own personalization to your environments, we recommend storing your preferred tooling and configuration in source controlled dotfiles.
New image tags can be published by image writers. These new image tags may contain updated dependencies and tooling to help while developing the project.
The image tag that an environment is running is stored in the
cemanager and a user will be
notified when a newer image tag has been published for an environment.