Learn about environments in Novu
Novu runs all your requests in the context of an environment. By default, Novu creates two environments when your account was just created, development
and production
.
The development environment is used for testing purposes and validating notification changes prior to committing them to the production environment.
It will be your live/production environment, you cannot make changes to this environment directly. You will first have to make the changes in the development
environment and then promote it to production
. This is a read-only environment.
Novu will separate most of the data associated with your account based on the current accessed environment. This will include:
Each environment will be accessed using a separate credential set:
Provider Identifier
.Provider Identifier
. Even if you’re using two different integration of the same provider, you’ll have two different Provider Identifier
, each unique to one integration. For example, if you’ve two slack integrations, they will have two different Provider Identifier
.Novu API
from your backend services.We suggest configuring these key sets based on your active environment, the same as you would use to manage different service credentials and serve them based on the current environment in which your code is deployed.
After making a change to a workflow or brand relating settings, this change will be added under the changes page in the admin panel.
A change is generated by making a difference between the development
environment and the target production
environment. All pending changes will be listed on the changes page.
A change can either be applied manually or by pressing the Promote all changes button.
Seeing All Changes in Novu Dashboard
Learn about environments in Novu
Novu runs all your requests in the context of an environment. By default, Novu creates two environments when your account was just created, development
and production
.
The development environment is used for testing purposes and validating notification changes prior to committing them to the production environment.
It will be your live/production environment, you cannot make changes to this environment directly. You will first have to make the changes in the development
environment and then promote it to production
. This is a read-only environment.
Novu will separate most of the data associated with your account based on the current accessed environment. This will include:
Each environment will be accessed using a separate credential set:
Provider Identifier
.Provider Identifier
. Even if you’re using two different integration of the same provider, you’ll have two different Provider Identifier
, each unique to one integration. For example, if you’ve two slack integrations, they will have two different Provider Identifier
.Novu API
from your backend services.We suggest configuring these key sets based on your active environment, the same as you would use to manage different service credentials and serve them based on the current environment in which your code is deployed.
After making a change to a workflow or brand relating settings, this change will be added under the changes page in the admin panel.
A change is generated by making a difference between the development
environment and the target production
environment. All pending changes will be listed on the changes page.
A change can either be applied manually or by pressing the Promote all changes button.
Seeing All Changes in Novu Dashboard