You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/platform/concepts/environments.mdx
+42-26Lines changed: 42 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,42 +4,55 @@ description: 'Understanding and managing environments in Novu'
4
4
icon: 'GitFork'
5
5
---
6
6
7
-
Novu uses environments to separate your development and production workflows. When you create an account, you'll get two default environments: `Development` and `Production`.
7
+
Novu uses environments to separate your development and production workflows. When you create an account, you'll get two default environments: **Development** and **Production**.
8
8
9
-
## Development Environment
9
+
## Development environment
10
10
11
-
Use the development environment to test new notification workflows, validate changes before deploying to production, and experiment with different configurations.
11
+
Use the development environment to build and test new workflows, layouts, translations, and experiment with different configurations before publishing to other environments.
12
12
13
-
## Production Environment
13
+
## Production environment
14
14
15
-
The production environment is your live environment where notifications are sent to real users. Use the production environment for production use cases, and other environments for non-production use cases.
15
+
The Production environment is your live environment, sending notifications to real users. To ensure stability and prevent unintended changes, this environment is view-only for workflows, layouts, and translations.
16
+
17
+
Changes are not made here directly but are pushed from the non production environment via the publishing process.
16
18
17
19
## Custom Environments
18
20
19
-
<Callouttype="info">Custom environments are available in Team and Enterprise plans.</Callout>
21
+
<Callouttype="info">Custom environments are available in <ahref="https://novu.co/pricing"target="_blank"rel="noopener noreferrer">Team and Enterprise plans</a>.</Callout>
20
22
21
23
Create custom environments to match your development workflow:
22
24
23
25
1. Go to the [Environments page](https://dashboard.novu.co/environments) in Novu dashboard
24
-
2. Click on the `Create environment` button on the top right.
25
-
3. A popup will appear. Enter names like `Staging` or `QA`.
26
+
2. Click on the **Create environment** button on the top right.
27
+
3. A menu will appear. Enter your preferred environment name.
26
28
4. Assign unique colors to easily distinguish between environments.
27
-
5. Click on `Create environment` button on the bottom right.
5. Click on **Create environment** button on the bottom right.
28
31
6. New environment will be created and will be available in the environments list.
29
32
30
-
## What's Unique to Each Environment?
33
+
## What's unique to each environment?
34
+
35
+
Each environment has a mix of isolated resources and assets that can be published from Development.
36
+
37
+
### Environment specific resources
31
38
32
-
Each environment maintains its own separate:
39
+
These resources are completely separate and unique to each environment. Data in one environment has no connection to data in another. They are:
33
40
34
41
- Subscribers
35
42
- Topics
36
-
- Workflows
37
-
- Webhooks
38
-
- Integrations
43
+
- Integrations (Provider credentials)
39
44
- API keys (application identifier and secret key)
40
45
- Activity feed
46
+
- Webhooks
47
+
48
+
### Publishable assets
41
49
42
-
## Environment Credentials
50
+
These assets are managed centrally in the Development environment and then published to other environments.
51
+
- Workflows
52
+
- Layouts
53
+
- Translations
54
+
55
+
### Environment Credentials
43
56
44
57
Each environment has two unique identifiers:
45
58
@@ -57,18 +70,21 @@ Each environment has two unique identifiers:
57
70
58
71
**Best Practice**: Configure these credentials in your application based on the active environment, similar to how you manage other service credentials.
59
72
60
-
## Promoting workflows between environments
73
+
## Publishing changes to other environments
74
+
75
+
Novu provides a publish mechanism that allows you to promote changes from your dvelopment environment to production or other custom environments. This process ensures that all changes are deliberate, reviewed, and deployed in a controlled manner.
61
76
62
-
One workflow can be synced to another environment using the `Sync Workflow` option in workflow actions. While syncing, Novu will give option to which environment to sync the workflow to. If workflow with same identifier is already present in the destination environment, it will be overwritten with the source workflow.
77
+
The publishing process bundles all modifications made to workflows, layouts, and translations since the last publish event.
63
78
64
-
Steps:
79
+
### How to publish changes
65
80
66
-
1. Go to the [Workflows page](https://dashboard.novu.co/workflows) in Novu dashboard
67
-
2. Click on the three dot menu in the workflow row
68
-
3. If you have more than two environments, hover over the `Sync Workflow` option to see the destination environment, then click it.
69
-
4. If you have only two environments, Click on the `Sync to <Environment Name>` option. Here `Environment Name` is the name of another environment.
70
-
5. The workflow will be synced to the destination environment.
81
+
After making modifications in your Development environment in the [Novu dashboard](https://dashboard.novu.co), you can promote them to another environment by following these steps:
71
82
72
-
<Callouttype="info">
73
-
Currently, a single workflow can be synced to another environment.
74
-
</Callout>
83
+
1. Ensure you are in the Development environment. All changes must originate from here.
84
+
2. Click the **Publish changes** button in the top right of the screen.
0 commit comments