Environments
How Environments work in Jet Admin
Last updated
Was this helpful?
How Environments work in Jet Admin
Last updated
Was this helpful?
Environments allow you to have multiple configurations of your project within Jet Admin. If you want to update the resource, add a new one, change the settings, or alter the UI, you can do it safely in a separate environment, whether it's staging or dev, and after the changes are reviewed and approved you can merge this new configuration into the production version. You also can create separate environments to control the updates: test the update on the staging environment and then push it into production.
By default, any new project is created in the production environment. To quickly add a new environment you need to
Click the Add Environment button in the project settings
Click on the Create button
Now you have a full copy of your production version where you can change, test, and troubleshoot without affecting the production version of the project.
To make sure your users always use a stable version of Jet, you can lock the production version of the project in the Production environment, and set the project version to "Latest" in the staging environment. This will keep the staging version up to date and allow you to test any new updates before approving it for production. To do so, follow the steps:
Click on the Jet Admin Version
From the dropdown menu, choose the Version and Save
Once you've made the changes in the staging or development environment, you can transfer those changes onto the production or any other environment. For that,
In any environment click Copy environment.
Select the environment you'd like to apply changes from and the environment you'd like to apply those changes for.
Click Copy
Any user who is invited into an existing environment can switch between environments. To do so, follow the steps:
Hover your mouse over the project icon (top right)
Select an environment from the drop-down.