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
Strapi Cloud: GitLab as new git provider + new signup page (#1942)
* Update deployment.md and all screenshots
* Mention GitLab whenever only GitHub was written as only git provider
* Add more updates for GitLab as new provider
* Add link to GitLab documentation
* Add prerequisite about GitLab permission required
Copy file name to clipboardExpand all lines: docusaurus/docs/cloud/getting-started/deployment.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,8 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have
15
15
16
16
* Strapi version `4.8.2` or higher
17
17
* Project database must be compatible with PostgreSQL. Strapi does not support and does not recommend using any external databases, though it's possible to configure one (see [advanced database configuration](/cloud/advanced/database)).
18
-
* Project(s) source code hosted on [GitHub](https://github.com). The connected repository can contain multiple Strapi applications. Each Strapi app must be in a separate directory.
18
+
* Project(s) source code hosted on [GitHub](https://github.com) or [GitLab](https://about.gitlab.com/). The connected repository can contain multiple Strapi applications. Each Strapi app must be in a separate directory.
19
+
* Specifically for GitLab: at least have "[Maintainer](https://docs.gitlab.com/ee/user/permissions.html)" permissions for the project to import on Strapi Cloud.
19
20
:::
20
21
21
22
## Logging in to Strapi Cloud
@@ -44,7 +45,7 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have
44
45
}}
45
46
/>
46
47
47
-
2. You will be redirected to the first project creation interface. This interface contains 3 steps: choosing a plan, connecting a GitHub repository, and setting up the project.
48
+
2. You will be redirected to the first project creation interface. This interface contains 3 steps: choosing a plan, connecting a git repository, and setting up the project.
48
49
49
50
<ThemedImage
50
51
alt="Strapi Cloud project creation, step 1"
@@ -60,19 +61,19 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have
60
61
Strapi Cloud offers a free trial for only one project and you will not need to share your credit card details to create your first project. Once the free trial has already been used for a previous project, the option will no longer appear in the plan selection.
61
62
:::
62
63
63
-
4. Connect a GitHub repository to your new Strapi Cloud project.
64
+
4. Connect a git repository to your new Strapi Cloud project.
64
65
65
66
:::strapi Choose your path to create your new Strapi Cloud project!
66
67
Select one of the tabs below depending on how you wish to proceed:
67
-
- by using a prebuilt template and creating a new GitHub repository to discover Strapi Cloud easily and quickly *(recommended for new users and beginners)*,
68
-
- or by using your own, already existing GitHub repository and Strapi project.
68
+
- by using a prebuilt template and creating a new repository on GitHub to discover Strapi Cloud easily and quickly *(recommended for new users and beginners — not available on another provider than GitHub)*,
69
+
- or by using your own, already existing GitHub or GitLab repository and Strapi project.
4.a. Click on the **Use template** button. If you are creating a project for the first time, you may first have to select GitHub as git provider and then you will see the option to use a template.
76
77
77
78
4.b. In the *Create repository with template* modal, choose:
78
79
@@ -106,18 +107,18 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have
4.a. Click on the **Connect GitHub repositories** button.
110
+
4.a. (optional) If you are creating a project for the first time, you may first have to select a git provider: either GitHub or GitLab. If you already created a project with one git provider, you can afterward create another project using another provider by clicking on the **Switch git provider** button and selecting either GitHub or GitLab.
110
111
111
112
:::tip
112
-
Connect the GitHub account and/or organizations that own the repository or repositories you want to deploy. This can be different from the account that owns the Strapi Cloud account.
113
+
Connect the GitHub or GitLab account and/or organizations that own the repository or repositories you want to deploy. This can be different from the account that owns the Strapi Cloud account.
113
114
:::
114
115
115
-
4.b. If you have already given Strapi Cloud access to all repositories of your GitHub account, go directly to the next step. If not, you will be redirected to a GitHub modal where you will have to allow Strapi Cloud permission to access your repositories (more information in the [GitHub documentation](https://docs.github.com/en/apps/overview)).
116
+
4.b. If you have already given Strapi Cloud access to all repositories of your GitHub or GitLab account, go directly to the next step. If not, you will be redirected to a modal where you will have to allow Strapi Cloud permission to access some or all your repositories on GitHub/GitLab (more information in the [GitHub](https://docs.github.com/en/apps/overview) and [GitLab](https://docs.gitlab.com/ee/integration/oauth_provider.html#view-all-authorized-applications) documentations).
116
117
117
118
4.c. Back in the project creation interface, select your *Account* and a *Repository*.
| Display name | Write the name of your Strapi app, this is fetched from the repository name but can be edited. It is automatically converted to slug format (`my-strapi-app`). |
138
-
|GitHub branch | Choose from the drop-down the default branch to use for this deployment. This uses the [default branch](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch) of the repository. |
139
+
|Git branch | Choose from the drop-down the default branch to use for this deployment. This uses the default branch of the repository. |
139
140
| Deploy on push | Check the box to automatically deploy the latest changes from the selected branch. When disabled, you will need to manually deploy the latest changes. |
140
141
| Region | Choose the geographic location of the servers where your Strapi application is hosted. Selected region can either be New York in North America (default) or Amsterdam in Europe. |
141
142
142
143
:::note
143
-
The GitHub branch and "Deploy on push" settings can be modified afterwards through the project's setting, however the project name and hosting region setting can only be chosen during the creation of the project (see [Project Settings](/cloud/projects/settings)).
144
+
The Git branch and "Deploy on push" settings can be modified afterwards through the project's setting, however the project name and hosting region setting can only be chosen during the creation of the project (see [Project Settings](/cloud/projects/settings)).
144
145
:::
145
146
146
147
5.b. (optional) Click on **Show advanced settings** to fill in the following options:
Copy file name to clipboardExpand all lines: docusaurus/docs/cloud/getting-started/intro.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Strapi Cloud is a managed content platform built on top of Strapi, the leading o
15
15
16
16
Strapi Cloud enables you to increase your content velocity without having to compromise on customization needs and requirements. Development teams can rely on Strapi Cloud to abstract away the complexity of infrastructure management while keeping your development workflow and extending the core capabilities of Strapi. Content managers can use Strapi Cloud to autonomously manage all types of content and benefit from a complete set of content collaboration, security, and compliance features.
17
17
18
-
The typical workflow is to create your Strapi (v4.8.2 or later) application locally, extend the application with plugins or custom code, version the application's codebase through GitHub, and deploy the application in seconds with Strapi Cloud (see [deployment and prerequisites](/cloud/getting-started/deployment#prerequisites)).
18
+
The typical workflow is to create your Strapi (v4.8.2 or later) application locally, extend the application with plugins or custom code, version the application's codebase through your git provider (GitHub or GitLab), and deploy the application in seconds with Strapi Cloud (see [deployment and prerequisites](/cloud/getting-started/deployment#prerequisites)).
Copy file name to clipboardExpand all lines: docusaurus/docs/cloud/projects/settings.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
@@ -15,7 +15,7 @@ The *Project Settings* page enables you to manage the configuration and settings
15
15
The *General* tab enables you to check and update the following options for the project:
16
16
17
17
- Details: to see the name of your Strapi Cloud project, used to identify the project on the Cloud Dashboard, Strapi CLI, and deployment URLs. The project name is set at project creation (see [Deployment](/cloud/getting-started/deployment)) and cannot be modified afterwards.
18
-
- Connected Git repository: to change the branch of the GitHub repository used for your project (see [Modifying GitHub repository branch](#modifying-github-repository-branch)).
18
+
- Connected git repository: to change the branch of the GitHub or GitLab repository used for your project (see [Modifying git repository branch](#modifying-git-repository-branch)).
19
19
- Selected region: to see the hosting region of the project, meaning the geographical location of the servers where the project and its data and resources are stored. The hosting region is set at project creation (see [Deployment](/cloud/getting-started/deployment)) and cannot be modified afterwards.
20
20
- Debug info: to see the internal project name for the project. This is useful for support purposes.
21
21
- Delete project: to permanently delete your Strapi Cloud project (see [Deleting Strapi Cloud project](#deleting-strapi-cloud-project)).
@@ -28,11 +28,11 @@ The *General* tab enables you to check and update the following options for the
28
28
}}
29
29
/>
30
30
31
-
### Modifying GitHub repository branch
31
+
### Modifying git repository branch
32
32
33
-
The GitHub repository branch and base directory for a Strapi Cloud project are by default chosen at the creation of the project (see [Creating a project](/cloud/getting-started/deployment)). Both can afterwards be edited via the project's settings.
33
+
The GitHub or Gitlab repository branch and base directory for a Strapi Cloud project are by default chosen at the creation of the project (see [Creating a project](/cloud/getting-started/deployment)). Both can afterwards be edited via the project's settings.
34
34
35
-
1. In the *Connected Git repository* section of the *General* tab, click on the **Edit** button.
35
+
1. In the *Connected git repository* section of the *General* tab, click on the **Edit** button.
36
36
2. In the *Edit Git settings* dialog, edit the available options of your choice:
0 commit comments