mirror of
https://github.com/ToolJet/ToolJet
synced 2026-04-22 14:07:26 +00:00
9f2ff94a12
* whtie label revamp * minor changes * updated beta info in copilot docs * renamed gds to ds in overview doc of v2.15 onwards * updated multienv: renamed gds to ds, updated screenshot * updated multienv: app state description * updated superadmin wrt new licensing updates * licensing update: free trial * updates in licensing * changes after review * [docs]updated restapi with bearer auth * Update kubernetes-aks.md * Update openshift.md * Update ecs.md * Update ecs.md * Update kubernetes-gke.md * Update kubernetes.md * Update docker.md * Update docker.md * Update ecs.md * Update google-cloud-run.md * Update kubernetes-aks.md * Update kubernetes-gke.md * Update kubernetes.md * Update openshift.md * Update kubernetes-gke.md * Update kubernetes-aks.md * fixed ecs, removed heroku from 2.15 onwards * updated digitalocean doc * licensing doc changes and location * Update digitalocean.md * Update digitalocean.md * added v2.18.0 --------- Co-authored-by: Adish M <44204658+adishM98@users.noreply.github.com>
60 lines
2.1 KiB
Markdown
60 lines
2.1 KiB
Markdown
---
|
|
id: multi-environment
|
|
title: Multi-Environment
|
|
---
|
|
|
|
<div className='badge badge--primary heading-badge'>Available on: Enterprise Edition</div>
|
|
|
|
ToolJet's **multi-environment** helps in streamlining workflows, thereby minimizing the chances of errors, and enables effective application management. Using multi-environment ensures that your ToolJet application is rigorously tested before it is made available to users.
|
|
|
|
<div style={{textAlign: 'center'}}>
|
|
|
|
<img className="screenshot-full" src="/img/v2-beta/multi-env/multienv.png" alt="Multi-Environment" />
|
|
|
|
</div>
|
|
|
|
### Environments
|
|
|
|
ToolJet provides three default **environments**:
|
|
- **Production**
|
|
- **Development**
|
|
- **Staging**
|
|
|
|
:::info
|
|
The default environments cannot be removed or renamed.
|
|
:::
|
|
|
|
### Configuring connections for environments
|
|
|
|
To configure connection settings for different environments, follow these steps:
|
|
|
|
1. Go to the **[Global Datasource](/docs/data-sources/overview)** page.
|
|
2. Click on the **Add new datasource** button.
|
|
3. Choose a datasource. In the connection modal, you'll find three tabs: **Production**, **Staging**, and **Development**.
|
|
4. Switch to each tab and enter the appropriate credentials for connecting to the respective database. Remember to save after entering credentials on each tab.
|
|
|
|
<div style={{textAlign: 'center'}}>
|
|
|
|
<img className="screenshot-full" src="/img/v2-beta/multi-env/envconnect.gif" alt="Multi-Environment" />
|
|
|
|
</div>
|
|
|
|
### Switching environments
|
|
|
|
To switch between environments, follow these steps:
|
|
|
|
1. Click on the **Environment Manager** located on the top bar of the app builder.
|
|
2. The dropdown menu will open, allowing you to select an environment.
|
|
|
|
<div style={{textAlign: 'center'}}>
|
|
|
|
<img className="screenshot-full" src="/img/v2-beta/multi-env/switch.png" alt="Multi-Environment" />
|
|
|
|
</div>
|
|
|
|
ToolJet's app builder remembers your last editing state. When you reopen an app, it resumes from where you left off, ensuring a seamless experience. For instance, if you edited an app in the staging environment, it will open in the staging environment when you return.
|
|
|
|
:::info
|
|
The default environment for released apps is **Production**.
|
|
:::
|
|
|