Update content for environments page #1008
Open
+98
−97
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
DianaHackmamba
requested changes
Nov 17, 2025
|
|
||
| - **Development environment**: Use the development environment to build and test new workflows, layouts, translations, and experiment with different configurations before publishing to other environments. | ||
|
|
||
| - **Production environment**: The production environment is used to send notifications to your subscribers. To ensure stability and prevent unintended changes, this environment is view-only for workflows, layouts, and translations. Changes are not made here directly, they are made from other environment and then published to this production environment. |
Contributor
There was a problem hiding this comment.
Suggested change
| - **Production environment**: The production environment is used to send notifications to your subscribers. To ensure stability and prevent unintended changes, this environment is view-only for workflows, layouts, and translations. Changes are not made here directly, they are made from other environment and then published to this production environment. | |
| - **Production environment**: The production environment is used to send notifications to your subscribers. To ensure stability and prevent unintended changes, this environment is view-only for workflows, layouts, and translations. Changes are not made here directly, they are made from other environments and then published to this production environment. |
Contributor
There was a problem hiding this comment.
Should we just say that the changes go from development to production? As written, it sounds like there is more than one possibility. I get that some folx will have custom environments that they might push changes from, but it sounds like the most standard will be dev to prod.
| To create a custom environment: | ||
|
|
||
| 1. Log in to the Novu dashboard. | ||
| 2. Go to the [Environments page](https://dashboard.novu.co/environments) in Novu dashboard |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. Go to the [Environments page](https://dashboard.novu.co/environments) in Novu dashboard | |
| 2. Go to the [Environments page](https://dashboard.novu.co/environments) in the Novu dashboard. |
|
|
||
| 1. Log in to the Novu dashboard. | ||
| 2. Go to the [Environments page](https://dashboard.novu.co/environments) in Novu dashboard | ||
| 3. Click on the **Create environment** button on the top right. |
Contributor
There was a problem hiding this comment.
Suggested change
| 3. Click on the **Create environment** button on the top right. | |
| 3. Click **Create environment**. A menu appears. |
| 1. Log in to the Novu dashboard. | ||
| 2. Go to the [Environments page](https://dashboard.novu.co/environments) in Novu dashboard | ||
| 3. Click on the **Create environment** button on the top right. | ||
| 4. A menu will appear. Enter your preferred environment name. |
Contributor
There was a problem hiding this comment.
Suggested change
| 4. A menu will appear. Enter your preferred environment name. | |
| 4. Enter your preferred environment name. |
Contributor
There was a problem hiding this comment.
I there a field I should enter the name in?
| 4. A menu will appear. Enter your preferred environment name. | ||
| 5. Assign unique colors to easily distinguish between environments. | ||
|  | ||
| 6. Click on **Create environment** button on the bottom right. |
Contributor
There was a problem hiding this comment.
Suggested change
| 6. Click on **Create environment** button on the bottom right. | |
| 6. Click **Create environment**. |
|
|
||
| Each environment has two unique identifiers: | ||
|
|
||
| 1. **Application Identifier** |
Contributor
There was a problem hiding this comment.
Why is this a numbered list? And why title case?
| You can promote changes to other environments by following these steps: | ||
|
|
||
| 1. Ensure you are in the **Development** environment. All changes must originate from here. | ||
| 2. Click the **Publish changes** button in the top right of the screen. |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. Click the **Publish changes** button in the top right of the screen. | |
| 2. Click **Publish changes**. A list of available environments appears. |
| 1. Ensure you are in the **Development** environment. All changes must originate from here. | ||
| 2. Click the **Publish changes** button in the top right of the screen. | ||
|  | ||
| 3. A list of available environments will appear. Select the environment you want to publish to. |
Contributor
There was a problem hiding this comment.
Suggested change
| 3. A list of available environments will appear. Select the environment you want to publish to. | |
| 3. Select the environment that you want to publish to. |
|  | ||
| 3. A list of available environments will appear. Select the environment you want to publish to. | ||
|  | ||
| 4. A menu will open showing all the availabl workflows. Select the checkboxes next to the workflows you want to publish. |
Contributor
There was a problem hiding this comment.
Suggested change
| 4. A menu will open showing all the availabl workflows. Select the checkboxes next to the workflows you want to publish. | |
| 4. Select the checkboxes next to the workflows that you want to publish. A menu appears, showing all the available workflows. |
|  | ||
| 4. A menu will open showing all the availabl workflows. Select the checkboxes next to the workflows you want to publish. | ||
|  | ||
| 5. Click the publish button to publish the selected workflows to the selected environment. No newline at end of file |
Contributor
There was a problem hiding this comment.
Not "Click Publish"?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.