Skip to content

Commit 344cc22

Browse files
authored
Small change to previews
1 parent 0977975 commit 344cc22

1 file changed

Lines changed: 6 additions & 10 deletions

File tree

  • www/apps/cloud/app/environments/preview

www/apps/cloud/app/environments/preview/page.mdx

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,16 @@ Learn more about what environments are and their types in the [Environments](../
1616

1717
## Preview (Short-Lived) Environment Infrastructure
1818

19-
Preview environments are designed for testing changes before merging them into production. So, they have a simpler setup compared to production environments:
19+
Preview environments are designed for testing changes before merging them into production. So, they have a simpler setup compared to [production environments](../long-lived/page.mdx):
2020

2121
- Medusa automatically scales preview environments to zero after ten minutes of inactivity. So, if no one is using the preview environment, it will automatically shut down to save resources.
2222
- Preview environments run on a single server instance, which is sufficient for testing changes.
2323

24-
The simpler setup is sufficient for testing changes. However, some customizations like scheduled jobs and subscribers may not work as expected since the preview environment may be inactive. You can still use these customizations in long-lived environments normally.
24+
### Preview Environment Inactivity
25+
26+
Since Preview environments are only meant for testing, they are put to sleep after ten minutes of inactivity.
27+
28+
So, if you're testing scheduled jobs or events, they may not work as expected in preview environments. They will work as expected in long-lived environments, such as Staging or Production.
2529

2630
---
2731

@@ -108,14 +112,6 @@ You can change the environment from which the preview environment's database is
108112

109113
---
110114

111-
## Preview Environment Inactivity
112-
113-
Since Preview environments are only meant for testing, they are put to sleep after ten minutes of inactivity.
114-
115-
So, if you're testing scheduled jobs or events, they may not work as expected in preview environments. They will work as expected in long-lived environments, such as Staging or Production.
116-
117-
---
118-
119115
## Delete Preview Environment
120116

121117
Preview environments are automatically deleted when their PR is merged or closed. However, you can also delete them manually if needed.

0 commit comments

Comments
 (0)