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: docusaurus/docs/cloud/advanced/database.md
-8Lines changed: 0 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,14 +62,6 @@ To ensure a smooth deployment, it is recommended to not change the names of the
62
62
63
63
To deploy the project and utilize the external database, push the changes from earlier. This will trigger a rebuild and new deployment of the Strapi Cloud project.
64
64
65
-
<ThemedImage
66
-
alt="Deployment"
67
-
sources={{
68
-
light: '/img/assets/cloud/deploy-logs.png',
69
-
dark: '/img/assets/cloud/deploy-logs_DARK.png',
70
-
}}
71
-
/>
72
-
73
65
Once the application finishes building, the project will use the external database.
|**Assets Bandwidth**| 50GB | 50GB per month | 500GB per month | 1,000GB per month |
@@ -30,7 +30,8 @@ Strapi Cloud offers a free 14 days trial for all new accounts, and 3 paid plans:
30
30
|**Review Workflows**| up to 2 | N/A | N/A | up to 2 |
31
31
|**Content History**| 14 days retention | N/A | 14 days retention | 90 days retention |
32
32
||||||
33
-
|**Backups**| N/A | N/A | Weekly | Weekly |
33
+
|**Backups**| N/A | N/A | Weekly | Daily |
34
+
|**Environments**| N/A | N/A | 0 included (up to 99 extra) | 1 included (up to 99 extra) |
34
35
35
36
:::strapi Additional information on usage and features
36
37
- General features & usage:
@@ -44,14 +45,22 @@ Strapi Cloud offers a free 14 days trial for all new accounts, and 3 paid plans:
44
45
- Releases refers to the maximum number of pending releases that can be created (see [Releases in User Guide](/user-docs/releases/introduction) for more information).
45
46
- Review Workflows refers to the maximum number of workflows that can be created and used (see [Review Workflows in User Guide](/user-docs/settings/review-workflows) for more information).
46
47
- Content History refers to the maximum numbers of days kept in history (see [Content History in User Guide](/user-docs/content-manager/working-with-content-history))
47
-
- Cloud specific feature: Backups refers to the automatic backups of Strapi Cloud projects (see [dedicated page in Cloud documentation](/cloud/projects/settings#backups) for more information).
48
+
- Cloud specific feature:
49
+
- Backups refers to the automatic backups of Strapi Cloud projects (see [Backups documentation](/cloud/projects/settings#backups) for more information on the feature).
50
+
- Environments refers to the number of environments included in the plan on top of the default production environment (see [Environments](/cloud/projects/settings#environments--) documentation for more information on the feature).
48
51
:::
49
52
53
+
## Environments management
54
+
55
+
Environments are isolated instances of your Strapi Cloud project. All projects have a default production environment, but other additional environments can be configured for projects on a Pro or Team plan, from the *Environments* tab of a project's settings (see [Environments](/cloud/projects/settings#environments--)). There is no limit to the number of additional environments that can be configured for a Strapi Cloud project.
56
+
57
+
The usage limits of additional environments are the same as for the project's production environment (e.g. an additional environment on the Pro plan will be limited at 150GB for assets storage, and overages will be charged the same way as for the production environment). Note however that the assets bandwidth and API calls are project-based, not environment-based, so these usage limits do not change even with additional environments.
58
+
50
59
## Seats management
51
60
52
61
Seats represent the maximum number of users that can access the Strapi admin panel. Each plan comes with a default number of seats.
53
62
54
-
You can add more seats either by upgrading to a higher plan, or manually adding individual seats as desired. Seats can be added from the **Billing & Usage** tab of a project's settings (see [Managing project's number of seats](/cloud/projects/settings#managing-projects-number-of-seats)).
63
+
You can add more seats either by upgrading to a higher plan, or manually adding individual seats as desired. Seats can be added from the *Billing & Usage* tab of a project's settings (see [Managing project's number of seats](/cloud/projects/settings#managing-projects-number-of-seats)).
55
64
56
65
There is however a maximum number of seats that can be added per plan:
Copy file name to clipboardExpand all lines: docusaurus/docs/cloud/projects/deploys-history.md
+14-15Lines changed: 14 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,17 +14,17 @@ tags:
14
14
15
15
# Deploy history and logs
16
16
17
-
For each Strapi Cloud project, you can access the history of all deployments that occured and their details including build and deploy logs. This information is available in the *Deploys* tab, located in the header of any chosen project.
17
+
For each Strapi Cloud project, you can access the history of all deployments that occured and their details including build and deploy logs. This information is available in the *Deployments* tab.
18
18
19
19
## Viewing deploy history
20
20
21
-
In the *Deploys* tab is displayed a chronological list of cards with the details of all historical deployments for your project.
21
+
In the *Deployments* tab is displayed a chronological list of cards with the details of all historical deployments for your project.
22
22
23
23
<ThemedImage
24
24
alt="Project deploys"
25
25
sources={{
26
-
light: '/img/assets/cloud/deploys.png',
27
-
dark: '/img/assets/cloud/deploys_DARK.png',
26
+
light: '/img/assets/cloud/overview.png',
27
+
dark: '/img/assets/cloud/overview_DARK.png',
28
28
}}
29
29
/>
30
30
@@ -41,25 +41,24 @@ Each card displays the following information:
41
41
42
42
## Accessing deployment details & logs
43
43
44
-
From the *Deploys* tab, you can click on the **See logs** button of any chosen deployment card to be redirected to the *Log details*. It contains the deployment's details logs.
44
+
From the *Deployments* tab, you can hover a deployment card to make the **Show details** button appear. Clicking on this button will redirect you to the *Deployment details* page which contains the deployment's detailed logs.
45
45
46
46
<ThemedImage
47
47
alt="Deployment details"
48
48
sources={{
49
-
light: '/img/assets/cloud/deploy-logs.png',
50
-
dark: '/img/assets/cloud/deploy-logs_DARK.png',
49
+
light: '/img/assets/cloud/deploy_logs.png',
50
+
dark: '/img/assets/cloud/deploy_logs_DARK.png',
51
51
}}
52
52
/>
53
53
54
-
In the *Deploy details* section of the *Log details* page is displayed the following information:
55
-
-*Status*, which can be *Building*, *Deploying*, *Done*, *Cancelled*, *Build failed*, or *Deploy failed*
56
-
-*Maintenance*: when the deployment occured
57
-
-*Deployed in*: the amount of time the deployment took
58
-
-*Commit*: the commit SHA <Annotation>💡 The commit SHA (or hash) is the unique ID of your commit, which refers to a specific change that was made at a specific time.</Annotation>, with a direct link to your git provider, and commit message used for this deployment
59
-
-*Branch*: the branch used for this deployment
60
-
61
-
In the *Logs* section of the *Log details* page you can click on the arrow buttons  to show or hide the build and deploy logs of the deployment.
54
+
In the *Build logs* and *Deployment logs* sections of the page you can click on the arrow buttons  to show or hide the build and deployment logs of the deployment.
62
55
63
56
:::tip
64
57
Click the **Copy to clipboard** button to copy the log contents.
65
58
:::
59
+
60
+
In the right side of the *Deployment details* page is also displayed the following information:
61
+
-*Commit*: the commit SHA <Annotation>💡 The commit SHA (or hash) is the unique ID of your commit, which refers to a specific change that was made at a specific time.</Annotation>, with a direct link to your git provider, and commit message used for this deployment
62
+
-*Status*, which can be *Building*, *Deploying*, *Done*, *Cancelled*, *Build failed*, or *Deploy failed*
63
+
-*Source*: the branch and commit message for this deployment
64
+
-*Duration*: the amount of time the deployment took and when it occured
Copy file name to clipboardExpand all lines: docusaurus/docs/cloud/projects/deploys.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Ongoing deployments can also be [manually cancelled](#cancelling-a-deployment) i
24
24
25
25
## Triggering a new deployment
26
26
27
-
To manually trigger a new deployment for your project, click on the **Trigger deploy** button always displayed in the right corner of a project dashboard's header. This action will add a new card in the *Deploys* tab, where you can monitor the status and view the deployment logs live (see [Deploy history and logs](/cloud/projects/deploys-history)).
27
+
To manually trigger a new deployment for your project, click on the **Trigger deployment** button always displayed in the right corner of a project dashboard's header. This action will add a new card in the *Deployments* tab, where you can monitor the status and view the deployment logs live (see [Deploy history and logs](/cloud/projects/deploys-history)).
28
28
29
29
<ThemedImage
30
30
alt="Triggering new deploy"
@@ -38,11 +38,11 @@ To manually trigger a new deployment for your project, click on the **Trigger de
38
38
39
39
If for any reason you want to cancel an ongoing and unfinished deployment:
40
40
41
-
1. Go to the *Log details* page of the deployment (see [Accessing log details](/cloud/projects/deploys-history#accessing-deployment-details--logs)).
42
-
2. Click on the **Cancel deploy** button in the top right corner. The status of the deployment will automatically change to *Cancelled*.
41
+
1. Go to the *Deployment details* page of the latest triggered deployment (see [Accessing log details](/cloud/projects/deploys-history#accessing-deployment-details--logs)).
42
+
2. Click on the **Cancel deployment** button in the top right corner. The status of the deployment will automatically change to *Cancelled*.
43
43
44
44
:::tip
45
-
You can also cancel a deployment from the *Deploys* tab which lists the deployments history. The card of ongoing deployment with the *Building* status will display a **Cancel deploy** button.
45
+
You can also cancel a deployment from the *Deployments* tab which lists the deployments history. The card of ongoing deployment with the *Building* status will display a  button for cancelling the deployment.
Copy file name to clipboardExpand all lines: docusaurus/docs/cloud/projects/overview.md
+22-23Lines changed: 22 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,8 @@ tags:
10
10
pagination_next: cloud/projects/settings
11
11
---
12
12
13
+
import ScreenshotNumberReference from '/src/components/ScreenshotNumberReference.jsx';
14
+
13
15
# Projects overview
14
16
15
17
The *Projects* page displays a list of all your Strapi Cloud projects. From here you can manage your projects and access the corresponding applications.
@@ -29,39 +31,36 @@ Each project card displays the following information:
29
31
**Disconnected*, if the project repository is not connected to Strapi Cloud
30
32
**Suspended*, if the project has been suspended (refer to [Project suspension](/cloud/getting-started/usage-billing#project-suspension) to reactivate the project)
31
33
**Incompatible version*, if the project is using a Strapi version that is not compatible with Strapi Cloud
32
-
* the last deployment date
33
34
34
35
Each project card also displays a  menu icon to access the following options:
35
36
***Visit App**: to be redirected to the application
36
-
***Go to Deploys**: to be redirected to the [*Deploys*](/cloud/projects/deploys) page
37
+
***Go to Deployments**: to be redirected to the [*Deploys*](/cloud/projects/deploys) page
37
38
***Go to Settings**: to be redirected to the [*Settings*](/cloud/projects/settings) page
38
39
39
-
## Accessing a project's overview
40
-
41
-
From the *Projects* page, click on any project card to access the *Overview* of your project. It displays all details such as usage and status information and gives access to deployment history and available settings.
Once you click on a project page, you access the dedicated dashboard for your chosen project. It is by default that you land on the *Overview* tab, however the header of the project's dashboard doesn't change and always offers the following options:
40
+
## Accessing a project's dashboard
45
41
46
-
- links to the other available tabs for the project: *Overview*, [*Deploys*](/cloud/projects/deploys), [*Runtime Logs*](/cloud/projects/runtime-logs) and [*Settings*](/cloud/projects/settings)
47
-
- the **Share** button to invite a new maintainer to collaborate on your project — and if the project is already shared: avatars of the maintainers (see [Collaboration](/cloud/projects/collaboration))
48
-
- the **Trigger deploy** button to trigger a new deployment of your project
49
-
- the **Visit app** button to access your application
50
-
:::
42
+
From the *Projects* page, click on any project card to access is dashboard. It displays the project and environment details and gives access to the deployment history and all available settings.
51
43
52
44
<ThemedImage
53
45
alt="Project overview"
54
46
sources={{
55
-
light: '/img/assets/cloud/overview.png',
56
-
dark: '/img/assets/cloud/overview_DARK.png',
47
+
light: '/img/assets/cloud/overview2.png',
48
+
dark: '/img/assets/cloud/overview2_DARK.png',
57
49
}}
58
50
/>
59
51
60
-
From the *Overview* tab, you can:
61
-
- view a recap of the main settings of your project, such as:
62
-
- the link to the source repository
63
-
- the name of the branch
64
-
- the name of the base directory
65
-
- the URL and link to the application
66
-
- view your project's usage (see [Usage](/cloud/getting-started/usage-billing) for more information)
67
-
- view your project's latest deploys (see [Deploys](/cloud/projects/deploys) for more information)
52
+
From the dashboard's header of a chosen project, you can:
53
+
- use the **Share** button to invite users to collaborate on the project (see [Collaboration](/cloud/projects/collaboration)) and see the icons of those who have already been invited <ScreenshotNumberReferencenumber="1" />,
54
+
- use the **Settings** button to access the settings of the project and its existing environments <ScreenshotNumberReferencenumber="2" />,
55
+
- choose which environment to visualise for the project <ScreenshotNumberReferencenumber="3" />,
56
+
- trigger a new deployment (see [Deployments management](/cloud/projects/deploys)) and visit your application <ScreenshotNumberReferencenumber="4" />.
57
+
58
+
Your project's dashboard also displays:
59
+
- the *Deployments* and *Runtime logs* tabs, to see the deployments history (more details in [Deploy history and logs](/cloud/projects/deploys-history)) and the runtime logs of the project (see [dedicated documentation page](/cloud/projects/runtime-logs)) <ScreenshotNumberReferencenumber="5" />
60
+
- the project and environment details in a box on the right of the interface <ScreenshotNumberReferencenumber="6" />, including:
61
+
- the number of API calls and database entries,
62
+
- the current usage for assets bandwidth and storage,
63
+
- the name of the branch and a **Manage** button to be redirect to the branch settings (see [Modifying git repository & branch](/cloud/projects/settings#modifying-git-repository--branch)),
0 commit comments