diff --git a/docusaurus/docs/cloud/account/account-billing.md b/docusaurus/docs/cloud/account/account-billing.md index 6247393e01..b4e37f6a32 100644 --- a/docusaurus/docs/cloud/account/account-billing.md +++ b/docusaurus/docs/cloud/account/account-billing.md @@ -13,80 +13,70 @@ tags: --- import NotV5 from '/docs/snippets/_not-updated-to-v5.md' +import InvoiceStatus from '/docs/snippets/invoices-statuses.md' -# Account billing details +# Account billing & invoices - + -Through the *Profile* page, accessible by clicking on your profile picture on the top right hand corner of the interface then clicking on **Profile**, you can access the *Billing* tab. +Through the *Profile* page, accessible by clicking on your profile picture on the top right hand corner of the interface then clicking on **Profile**, you can access the [![Billing icon](/img/assets/icons/CreditCard.svg) *Billing*](#account-billing) and [![Invoices icon](/img/assets/icons/Invoice.svg) *Invoices*](#account-invoices) tabs. -The *Billing* tab displays and enables you to modify the billing details and payment method set for the account. This information will by default be reused for every new project created with your Strapi Cloud account. +## Account billing -:::note -The Payment method section can only be accessible once the mandatory fields of the Billing details section have been filled in. -::: +The ![Billing icon](/img/assets/icons/CreditCard.svg) *Billing* tab displays and enables you to modify the billing details and payment method set for the account. -## Managing subscriptions +The *Payment method* section of the ![Billing icon](/img/assets/icons/CreditCard.svg) *Billing* tab allows you to manage the credit cards that can be used for the Strapi Cloud projects. The *Billing details* section requires to be filled in, at least for the mandatory fields, as this information will be the default billing details for all Strapi Cloud projects related to your account. -Using the **Manage subscriptions** button, you can view and manage your subscriptions, account and billing information, and payment method. +### Adding a new credit card -1. Click the **Manage subscriptions** button. A login modal will appear. +1. In the *Payment method* section of the ![Billing icon](/img/assets/icons/CreditCard.svg) *Billing* tab, click on the **Add card** button. +2. Fill in the following fields: -2. Enter the billing email address associated with your account and click **Continue**. A one-time password will be sent to the email address. +| Field name | Description | +| --- | --- | +| Card Number | Write the number of the credit card to add as payment method. | +| Expires | Write the expiration date of the credit card. | +| CVC | Write the 3-numbers code displayed at the back of the credit card. | -3. Enter the one-time password and click **Continue**. The **Manage Subscriptions** modal will appear. From here, you can: - - - view and edit your subscriptions by clicking on the active subscription(s) tile(s): change project name, update shipping details, [edit current subscription](#edit-subscription) and [cancel current subscription](#cancel-subscription) - - view and edit your Account Information: email, password, company name - - view and edit your Billing & Shipping Addresses - - view and edit your Payment Methods and add new ones - - access your Billing History and download your invoices +3. Click on the **Save** button. - +:::tip +The first credit card to be added as payment method for the account will by default be the primary one. It is however possible to define another credit card as primary by clicking on the ![Menu icon](/img/assets/icons/more.svg) icon, then **Switch as primary**. +::: -## Edit subscription +### Deleting a credit card -From the subscription management modal, you can view and modify any current subscription. +To remove a credit card from the list of payment methods for the account: - +1. Click on the ![Menu icon](/img/assets/icons/more.svg) icon of the credit card you wish to delete. +2. Click **Remove card**. The card is immediately deleted. + +:::note +You cannot delete the primary card as at least one credit card must be available as payment method, and the primary card is by default that one. If the credit card you wish to delete is currently the primary card, you must first define another credit card as primary, then delete it. +::: -1. Click on an active subscription tile (e.g. "Strapi Cloud Pro $99.00" located above the subscriptions management links such as *Account Information*, *Billing & Shipping Addresses*). You will be redirected to your subscription details. -2. Click on the **Edit Subscription** link. -3. If you only want to add addons (e.g. additional seats), click on the **Add Addons** button. -4. If you want to change plan (e.g. from Pro plan to Team plan), click on **Change** and select a new plan. -5. Confirm your modifications by clicking on the **Update Subscription** button at the bottom of the modal. +## Account invoices -## Cancel subscription +The ![Invoices icon](/img/assets/icons/Invoice.svg) *Invoices* tab displays the complete list of invoices for all your Strapi Cloud projects. -1. Click on an active subscription tile (e.g. "Strapi Cloud Pro $99.OO"). You will be redirected to your subscription details. -2. Click on the **Cancel Subscription** link. -3. Select the reason of your cancellation from the drop-down menu, and optionally add a comment in the textbox. -4. Confirm your choice by clicking on the **Confirm Cancellation** button. + + +:::strapi Invoices are also available per project. +In the *Settings > Invoices* tab of any project, you will find the invoices for that project only. Feel free to check the [dedicated documentation](/cloud/projects/settings#invoices). +::: diff --git a/docusaurus/docs/cloud/account/account-settings.md b/docusaurus/docs/cloud/account/account-settings.md index 7e3d617231..77c6a7ac38 100644 --- a/docusaurus/docs/cloud/account/account-settings.md +++ b/docusaurus/docs/cloud/account/account-settings.md @@ -16,15 +16,15 @@ import NotV5 from '/docs/snippets/_not-updated-to-v5.md' # Profile settings - + The *Profile* page enables you to manage your account details and preferences. It is accessible by clicking on your profile picture, on the top right hand corner of the interface, and **Profile**. -There are 3 tabs available in the *Profile* interface: [*General*](#general), [*Preferences*](#preferences) and *Billing* (the latter is documented in the [Account billing details](/cloud/account/account-billing) section of this documentation). +There are 3 tabs available in the *Profile* interface: ![General icon](/img/assets/icons/Faders.svg) [*General*](#general), ![Preferences icon](/img/assets/icons/Palette.svg) [*Preferences*](#preferences), ![Billing icon](/img/assets/icons/CreditCard.svg) *Billing* and ![Invoices icon](/img/assets/icons/Invoice.svg) Invoices (the last 2 are documented in the [Account billing details](/cloud/account/account-billing) section of this documentation). ## General -The *General* tab enables you to edit the following details for your account profile: +The ![General icon](/img/assets/icons/Faders.svg) *General* tab enables you to edit the following details for your account profile: - Details: to see the name associated with your account. - Connected accounts: to manage Google, GitHub and GitLab accounts connected with your Strapi Cloud account (see [Managing connected accounts](#managing-connected-accounts)). @@ -50,13 +50,13 @@ You can also click on the three dots button of a connected account and click on You can delete your Strapi Cloud account, but it will be permanent and irreversible. All associated projects and their data will be deleted as well and the subscriptions for the projects will automatically be canceled. -1. In the *Delete account* section of the *General* tab, click on the **Delete account** button. +1. In the *Delete account* section of the ![General icon](/img/assets/icons/Faders.svg) *General* tab, click on the **Delete account** button. 2. In the dialog, type `DELETE` in the textbox. 3. Confirm the deletion of your account by clicking on the **Delete** button. ## Preferences -The *Preferences* tab enables you to choose the appearance of your Strapi Cloud dashboard: either the Light or Dark theme. +The ![Preferences icon](/img/assets/icons/Palette.svg) *Preferences* tab enables you to choose the appearance of your Strapi Cloud dashboard: either the Light or Dark theme. General > Selected Region](/cloud/projects/settings#general)). +- Strapi can't provide security or support with external databases used with Strapi Cloud. +::: + + ## Configuration The project `./config/database.js` or `./config/database.ts` file must match the configuration found in the [environment variables in database configurations](https://docs.strapi.io/dev-docs/configurations/database#environment-variables-in-database-configurations) section. diff --git a/docusaurus/docs/cloud/cli/cloud-cli.md b/docusaurus/docs/cloud/cli/cloud-cli.md new file mode 100644 index 0000000000..35c50a7f0a --- /dev/null +++ b/docusaurus/docs/cloud/cli/cloud-cli.md @@ -0,0 +1,96 @@ +--- +sidebar_label: 'Cloud CLI' +displayed_sidebar: cloudSidebar +sidebar_position: 3 +tags: +- Strapi Cloud +- CLI +- deployment +--- + +import NotV5 from '/docs/snippets/_not-updated-to-v5.md' + +# Command Line Interface (CLI) + + + +Strapi Cloud comes with a Command Line Interface (CLI) which allows you to log in and out, and to deploy a local project without it having to be hosted on a remote git repository. The CLI works with both the `yarn` and `npm` package managers. + +:::note +It is recommended to install Strapi locally only, which requires prefixing all of the following `strapi` commands with the package manager used for the project setup (e.g `npm run strapi help` or `yarn strapi help`) or a dedicated node package executor (e.g. `npx strapi help`). +::: + +## strapi login + +**Alias:** `strapi cloud:login` + +Log in Strapi Cloud. + +```bash +strapi login +``` + +This command automatically opens a browser window to first ask you to confirm that the codes displayed in both the browser window and the terminal are the same. Then you will be able to log into Strapi Cloud via Google, GitHub or GitLab. Once the browser window confirms successful login, it can be safely closed. + +If the browser window doesn't automatically open, the terminal will display a clickable link as well as the code to enter manually. + +## strapi deploy + +**Alias:** `strapi cloud:deploy` + +Deploy a new local project (< 100MB) in Strapi Cloud. + +```bash +strapi deploy +``` + +This command must be used after the `login` one. It deploys a local Strapi project on Strapi Cloud, without having to host it on a remote git repository beforehand. The terminal will inform you when the project is successfully deployed on Strapi Cloud. + +Once the project is first deployed on Strapi Cloud with the CLI, the `deploy` command can be reused to trigger a new deployment of the same project. + +:::caution +The `deploy` command can only be used by new users who have never created a Strapi Cloud project, and for which the free trial is still available. Once a project is deployed with the CLI, it isn't possible to deploy another project on the same Strapi Cloud account with the CLI. +::: + +:::note +Once you deployed your project, if you visit the Strapi Cloud dashboard, you may see some limitations as well as impacts due to creating a Strapi Cloud project that is not in a remote repository and which was deployed with the CLI. + +- Some areas in the dashboard that are usually reserved to display information about the git provider will be blank. +- Some buttons, such as the **Trigger deploy** button, will be greyed out and unclickable since, unless you have [connected a git repository to your Strapi Cloud project](/cloud/getting-started/deployment-cli#automatically-deploying-subsequent-changes). +::: + +## strapi link + +**Alias:** `strapi cloud:link` + +Links project in current folder to an existing project in Strapi Cloud. + +```bash +strapi link +``` + +This command connects your local project in the current directory with an existing project on your Strapi Cloud account. You will be prompted to select the project you wish to link from a list of available projects hosted on Strapi Cloud. + +## strapi projects + +**Alias:** `strapi cloud:projects` + +Lists all Strapi Cloud projects associated with your account. + +```bash +strapi projects +``` + +This command retrieves and displays a list of all projects hosted on your Strapi Cloud account. + +## strapi logout + +**Alias:** `strapi cloud:logout` + +Log out of Strapi Cloud. + +```bash +strapi logout +``` + +This command logs you out of Strapi Cloud. Once the `logout` command is run, a browser page will open and the terminal will display a confirmation message that you were successfully logged out. You will not be able to use the `deploy` command anymore. diff --git a/docusaurus/docs/cloud/getting-started/cloud-fundamentals.md b/docusaurus/docs/cloud/getting-started/cloud-fundamentals.md new file mode 100644 index 0000000000..98a5469f80 --- /dev/null +++ b/docusaurus/docs/cloud/getting-started/cloud-fundamentals.md @@ -0,0 +1,23 @@ +--- +sidebar_label: 'Cloud fundamentals' +displayed_sidebar: cloudSidebar +slug: /cloud/cloud-fundamentals +sidebar_position: 1 +tags: +- Strapi Cloud +- concepts +--- + +# Strapi Cloud fundamentals + +Before going any further into this Strapi Cloud documentation, we recommend you to acknowledge the main concepts below. They will help you to understand how Strapi Cloud works, and ensure a smooth Strapi Cloud experience. + +- **Hosting Platform**
Strapi Cloud is a hosting platform that allows to deploy already existing Strapi projects created with Strapi CMS (Content Management System). Strapi Cloud is *not* the SaaS (Software as a Service) version of Strapi CMS. Feel free to refer to the [Developer Documentation](https://docs.strapi.io/dev-docs/intro) and [User Guide](https://docs.strapi.io/user-docs/intro) to learn more about Strapi CMS. + +- **Strapi Cloud Pricing Plans**
As a Strapi Cloud user you have the choice between 3 tiers: Developer, Pro and Team. Depending on the tier, you have access to different functionalities, support and customization options (see [Pricing page](https://strapi.io/pricing-cloud) for more details). In this Strapi Cloud documentation, the , , and badges can be displayed beside a section's title to indicate for which tier the feature is available. + +- **Strapi CMS Enterprise features**
Some of Strapi features, usually accessible via the Enterprise Edition of Strapi CMS, are included in some Strapi Cloud tiers (see [Pricing page](https://strapi.io/pricing-cloud) and [Information on billing & usage](/cloud/getting-started/usage-billing) for more details). These features, highlighted with an badge, are documented in the [User Guide](https://docs.strapi.io/user-docs/intro) and the [Developer Documentation](https://docs.strapi.io/dev-docs/intro). + +- **Types of Strapi Cloud users**
There can be 2 types of users on a Strapi Cloud project: owners and maintainers. The owner is the one who has created the project and has therefore access to all features and options for the project. Maintainers are users who have been invited to contribute to an already created project by its owner. Maintainers, as documented in the [Collaboration](/cloud/projects/collaboration) page, cannot view and access all features and options from the Strapi Cloud dashboard. + +- **Support**
The level of support provided by the Strapi Support team depends on the Strapi Cloud tier you subscribed for. The Developer and Pro tiers include Basic support while the Team tier includes Standard support. Please refer to the [dedicated support article](https://support.strapi.io/support/solutions/articles/67000680833-what-is-supported-by-the-strapi-team#Not-Supported) for all details regarding support levels. diff --git a/docusaurus/docs/cloud/getting-started/deployment-cli.md b/docusaurus/docs/cloud/getting-started/deployment-cli.md new file mode 100644 index 0000000000..cbe29b1086 --- /dev/null +++ b/docusaurus/docs/cloud/getting-started/deployment-cli.md @@ -0,0 +1,98 @@ +--- +title: with Cloud CLI +displayed_sidebar: cloudSidebar +description: Learn how to deploy your Strapi application via the CLI. +canonicalUrl: https://docs.strapi.io/cloud/getting-started/deployment-cli.html +sidebar_position: 2 +tags: +- Strapi Cloud +- deployment +- CLI +--- + +# Project deployment with the Command Line Interface (CLI) + +This is a step-by-step guide for deploying your project on Strapi Cloud for the first time, using the Command Line Interface. + +:::prerequisites +Before you can deploy your Strapi application on Strapi Cloud using the Command Line Interface, you need to have the following prerequisites: + +- Be a first-time Strapi Cloud user: you must never have deployed a project with Strapi Cloud before, and your free trial must still be available. +- Have a Google, GitHub or GitLab account. +- Have an already created Strapi project (see [Installing from CLI in the Developer Documentation](/dev-docs/installation/cli)), stored locally. The project must be less than 100MB. +- Have available storage in your hard drive where the temporary folder of your operating system is stored. +::: + +## Logging in to Strapi Cloud + +1. Open your terminal. + +2. Navigate to the folder of your Strapi project, stored locally on your computer. + +3. Enter the following command to log into Strapi Cloud: + + + + + ```bash + yarn strapi login + ``` + + + + + ```bash + npx run strapi login + ``` + + + + +4. In the browser window that opens automatically, confirm that the code displayed is the same as the one written in the terminal message. + +5. Still in the browser window, choose whether to login via Google, GitHub or GitLab. The window should confirm the successful login soon after. + +## Deploying your project + +1. From your terminal, still from the folder of your Strapi project, enter the following command to deploy the project: + + + + + ```bash + yarn strapi deploy + ``` + + + + + ```bash + npx run strapi deploy + ``` + + + + +2. Follow the progression bar in the terminal until confirmation that the project was successfully deployed with Strapi Cloud. + +### Automatically deploying subsequent changes + +By default, when creating and deploying a project with the Cloud CLI, you need to manually deploy again all subsequent changes by running the corresponding `deploy` command everytime you make a change. + +Another option is to enable automatic deployment through a git repository. To do so: + +1. Host your code on a git repository, such as [GitHub](https://www.github.com) or [GitLab](https://www.gitlab.com). +2. Connect your Strapi Cloud project to the repository (see the _Connected repository_ setting in [Projects Settings > General](/cloud/projects/settings#general)). +3. Still in _Projects Settings > General_ tab, tick the box for the "Deploy the project on every commit pushed to this branch" setting. From now on, a new deployment to Strapi Cloud will be triggered any time a commit is pushed to the connected git repository. + +:::note +Automatic deployment is compatible with all other deployment methods, so once a git repository is connected, you can trigger a new deployment to Strapi Cloud [from the Cloud dashboard](/cloud/projects/deploys), [from the CLI](/cloud/cli/cloud-cli#strapi-deploy), or by pushing new commits to your connected repository. +::: + +## ⏩ What to do next? + +Now that you have deployed your project via the Command Line Interface, we encourage you to explore the following ideas to have an even more complete Strapi Cloud experience: + +- Fill in your [billing information](/cloud/account/account-billing) to prevent your project from being suspended at the end of the trial period. +- Visit the Cloud dashboard to follow [insightful metrics and information](/cloud/projects/overview) on your Strapi project. +- Check out the full [Command Line Interface documentation](/cloud/cli/cloud-cli) to learn about the other commands available. diff --git a/docusaurus/docs/cloud/getting-started/deployment-options.md b/docusaurus/docs/cloud/getting-started/deployment-options.md new file mode 100644 index 0000000000..b74d6cbd90 --- /dev/null +++ b/docusaurus/docs/cloud/getting-started/deployment-options.md @@ -0,0 +1,24 @@ +--- +title: Project deployment +displayed_sidebar: cloudSidebar +description: Learn how to deploy your Strapi application on Strapi Cloud, via the Cloud dashboard or the CLI. +canonicalUrl: https://docs.strapi.io/cloud/getting-started/deployment-options.html +sidebar_position: 2 +tags: +- Strapi Cloud +- deployment +--- + +# Project deployment with Strapi Cloud + +You have 2 options to deploy your project with Strapi Cloud: + +- either with the user interface (UI), meaning that you will perform all the actions directly on the Strapi Cloud dashboard, +- or using the Cloud Comment Line Interface (CLI), meaning that you will only interact with a terminal. + +The guides below will guide you through all the steps for each of the deployment options. + + + + + diff --git a/docusaurus/docs/cloud/getting-started/deployment.md b/docusaurus/docs/cloud/getting-started/deployment.md index 43ec3c3a4e..1ce25f7973 100644 --- a/docusaurus/docs/cloud/getting-started/deployment.md +++ b/docusaurus/docs/cloud/getting-started/deployment.md @@ -1,5 +1,5 @@ --- -title: Project creation +title: with Cloud dashboard displayed_sidebar: cloudSidebar description: Learn how to deploy your Strapi application on Strapi Cloud. canonicalUrl: https://docs.strapi.io/cloud/getting-started/deployment.html @@ -14,16 +14,12 @@ tags: - Strapi Cloud plan --- -import NotV5 from '/docs/snippets/_not-updated-to-v5.md' +# Project deployment with the Cloud dashboard -# Project creation & deployment - - - -This is a step-by-step guide for creating and deploying your first project on Strapi Cloud. +This is a step-by-step guide for deploying your project on Strapi Cloud for the first time, using the Cloud dashboard. :::prerequisites -Before you can deploy your Strapi application on Strapi Cloud, you need to have the following prerequisites: +Before you can deploy your Strapi application on Strapi Cloud using the Cloud dashboard, you need to have the following prerequisites: * Strapi version `4.8.2` or higher * 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)). @@ -45,7 +41,7 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have }} /> -## Creating a project +## Deploying a project 1. From the *Projects* page, click the **Create project** button. @@ -57,7 +53,7 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have }} /> -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. +2. You will be redirected to the first project deployment interface. This interface contains 3 steps: choosing a plan, connecting a remote git repository, and setting up the project. -3. Choose a plan for your Strapi Cloud project: either Pro, Team, or the 14-days free trial. Feel free to refer to [Pricing](https://strapi.io/pricing-cloud) for more information. +3. Choose a plan for your Strapi Cloud project: either Developer, Pro, Team, or the 14-days free trial. Feel free to refer to [Pricing](https://strapi.io/pricing-cloud) for more information. - :::note - 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. + :::note Notes + - Strapi Cloud offers a free trial for only one project and you will not need to share your credit card details to deploy 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. + - You can't upload HTML files to Strapi Cloud during your free trial. ::: 4. Connect a git repository to your new Strapi Cloud project. - :::strapi Choose your path to create your new Strapi Cloud project! + :::strapi Choose your path for your new Strapi Cloud project! Select one of the tabs below depending on how you wish to proceed: - 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)*, - or by using your own, already existing GitHub or GitLab repository and Strapi project. @@ -85,7 +82,7 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have - 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. + 4.a. Click on the **Use template** button. If you are deploying 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. 4.b. In the *Create repository with template* modal, choose: @@ -105,7 +102,7 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have 4.d. 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 access to the newly created repository (more information in the [GitHub documentation](https://docs.github.com/en/apps/overview)). - 4.e. Back in the project creation interface, select your *Account* and the *Repository* you just created. + 4.e. Back in the project deployment interface, select your *Account* and the *Repository* you just created. - 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. + 4.a. (optional) If you are deploying a project for the first time, you may first have to select a git provider: either GitHub or GitLab. If you already deployed a project with one git provider, you can afterward deploy another project using another provider by clicking on the **Switch git provider** button and selecting either GitHub or GitLab. :::tip 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. @@ -127,7 +124,7 @@ Before you can deploy your Strapi application on Strapi Cloud, you need to have 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). - 4.c. Back in the project creation interface, select your *Account* and a *Repository*. + 4.c. Back in the project deployment interface, select your *Account* and a *Repository*. - + diff --git a/docusaurus/docs/cloud/getting-started/usage-billing.md b/docusaurus/docs/cloud/getting-started/usage-billing.md index c3c09fa21b..19c485606f 100644 --- a/docusaurus/docs/cloud/getting-started/usage-billing.md +++ b/docusaurus/docs/cloud/getting-started/usage-billing.md @@ -13,9 +13,9 @@ tags: import NotV5 from '/docs/snippets/_not-updated-to-v5.md' -# Usage & Billing +# Information on billing & usage - + This page contains general information related to the usage and billing of your Strapi Cloud account and projects. @@ -27,7 +27,7 @@ Strapi Cloud offers a free 14 days trial for all new accounts, and 3 paid plans: | **Database Entries** | 1,000 | 1,000 | 100,000 | 1,000,000 | | **Assets Storage** | 5GB | 15GB | 150GB | 500GB | | **Assets Bandwidth** | 50GB | 50GB per month | 500GB per month | 1,000GB per month | -| **API Requests** | 10,000 | 100,000 | 1,000,000 | 2,000,000 | +| **API Requests** | 10,000 | 100,000 | 1,000,000 | 10,000,000 | | | | | | | | **Audit Logs** | 7 days retention | N/A | N/A | 7 days retention | | **Releases** | 3 pending releases | N/A | N/A | 3 pending releases | @@ -55,7 +55,7 @@ Strapi Cloud offers a free 14 days trial for all new accounts, and 3 paid plans: Seats represent the maximum number of users that can access the Strapi admin panel. Each plan comes with a default number of seats. -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 **Account Settings** (see [Edit subscription](/cloud/account/account-billing#edit-subscription)). +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)). There is however a maximum number of seats that can be added per plan: @@ -108,86 +108,3 @@ If you don't pay the invoice, the subscription of your project will automaticall #### Project suspension for other reasons If your project was suspended for reasons other than unpaid invoice leading to subscription cancellation, you may not have the possibility to reactivate your project yourself. You should receive an email with instructions on how to resolve the issue. If you do not receive the email notification, please contact [Strapi Support](mailto:support@strapi.io). - - -# Usage & Billing - -This page contains general information related to the usage and billing of your Strapi Cloud account and projects. - -Strapi Cloud offers a free 14 days trial for all new accounts, and 2 paid plans: Pro and Team (see [Pricing page](https://strapi.io/pricing-cloud)). The usage-based pricing for Strapi Cloud is based on the following criteria and limits: - -| Feature | Free Trial | Pro | Team | -| --- | --- | --- | --- | -| **Seats** | 10 | 10 | 20 | -| **Database Entries** | 100,000 | 100,000 | 1,000,000 | -| **Assets Storage** | 5GB | 150GB | 500GB | -| **Assets Bandwidth** | 100GB | 500GB per month | 1,000GB per month | -| **API Requests** | 10,000 | 1,000,000 | 2,000,000 | -| **Audit Logs** | 7 days retention | N/A | 7 days retention | -| **Releases** | 3 pending releases | N/A | 3 pending releases | - -:::strapi Additional information on Strapi Cloud features -- Seats are the maximum number of users that can access the Strapi admin panel. -- Database entries are the number of entries in your database. -- Assets storage is the amount of storage used by your assets. -- Assets bandwidth is the amount of bandwidth used by your assets. -- API requests are the number of requests made to your APIs. This includes requests made to the GraphQL and REST APIs. -- Releases are the maximum number of pending [releases](/user-docs/releases/introduction) that can be created. -::: - -## Seats management - -Seats represent the maximum number of users that can access the Strapi admin panel. Each plan comes with a default number of seats. - -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 **Account Settings** (see [Edit subscription](/cloud/account/account-billing#edit-subscription)). - -There is however a maximum number of seats that can be added per plan: - -| Plan | Maximum Seats | -| --- | --- | -| **Free Trial** | 10 | -| **Pro** | 30 | -| **Team** | 50 | - - -## Billing - -Billing is based on the usage of your Strapi Cloud account and projects. You will be billed monthly for the usage of your account and applications. You can view your usage and billing information in the [Billing](https://cloud.strapi.io/profile/billing) section of your Strapi Cloud account. - -### Overages - -If you exceed the limits of your plan for API Requests, Asset Bandwidth, or Asset Storage, you will be charged for the corresponding overages. - -For example, if you exceed the 500GB limit in asset bandwidth of the Pro plan, you will be charged for the excess bandwidth at the end of the current billing period or on project deletion. Overages are not prorated and are charged in full. - -Overages are charged according to the following rates: - -| Feature | Rate | -| --- | --- | -| **API Requests** | $1.50 / 25k requests | -| **Asset Bandwidth** | $25.00 / 100GB | -| **Asset Storage** | $2.00/GB per month | - -### Project suspension - -Projects may end up in a **Suspended** state for various reasons, including: not paying the invoice, exceeding the limits of your free trial plan, or violating the [terms of service](https://strapi.io/cloud-legal). - -If your project is suspended, you will no longer be able to access the application or trigger new deployments. You will also be unable to access the Strapi admin panel. - -You can view the status of your project in the [Projects](https://cloud.strapi.io/projects) section of your Strapi Cloud account and you will be notified by email. - -:::warning -If you do not resolve the issue within 30 days, your suspended project will be deleted and all data will be permanently lost. To avoid this situation, you will be sent a first email when your project becomes suspended, then another email every 5 days until one week left, to remind you to solve the issue. The last week before the deletion of the project, you will be sent 3 more emails: 6 days, 3 days and 1 day before your project is finally deleted. -::: - -#### Project suspension after subscription cancellation - -If you don't pay the invoice, the subscription of your project will automatically be cancelled and the project will be suspended. You can reactivate the subscription through the billing modal (see [Edit subscription](/cloud/account/account-billing#edit-subscription)). - -1. Log into the billing modal and go to the *Subscription details* of the subscription associated with the suspended project. You should see a warning message confirming that the subscription was canceled for the following reason: "Not Paid". -2. Go back to the homepage of the billing modal, listing subscriptions and billing options. -3. Go to *Payment methods* and add a new, working card to pay the invoice. As soon as the invoice is paid, your project will automatically be reactivated. - -#### Project suspension for other reasons - -If your project was suspended for reasons other than unpaid invoice leading to subscription cancellation, you may not have the possibility to reactivate your project yourself. You should receive an email with instructions on how to resolve the issue. If you do not receive the email notification, please contact [Strapi Support](mailto:support@strapi.io). diff --git a/docusaurus/docs/cloud/projects/collaboration.md b/docusaurus/docs/cloud/projects/collaboration.md index 325fb5315a..2418bbb29c 100644 --- a/docusaurus/docs/cloud/projects/collaboration.md +++ b/docusaurus/docs/cloud/projects/collaboration.md @@ -16,6 +16,7 @@ import NotV5 from '/docs/snippets/_not-updated-to-v5.md' + Projects are created by a user via their Strapi Cloud account. Strapi Cloud users can share their projects to anyone else, so these new users can have access to the project dashboard and collaborate on that project, without the project owner to ever have to share their credentials. Users invited to collaborate on a project, called maintainers, do not have the same permissions as the project owner. Contrary to the project owner, maintainers: diff --git a/docusaurus/docs/cloud/projects/deploys.md b/docusaurus/docs/cloud/projects/deploys.md index b11535b521..e86bf3834a 100644 --- a/docusaurus/docs/cloud/projects/deploys.md +++ b/docusaurus/docs/cloud/projects/deploys.md @@ -20,8 +20,8 @@ import NotV5 from '/docs/snippets/_not-updated-to-v5.md' The creation of a new Strapi Cloud project automatically trigger the deployment of that project. After that, deployments can be: -- automatically triggered everytime a new commit is pushed to the branch (see [Project settings](/cloud/projects/settings#modifying-git-repository-branch)), -- or [manually triggered](#triggering-a-new-deployment) whenever needed. +- manually triggered whenever needed, [from the Cloud dashboard](#triggering-a-new-deployment) or [from the CLI](/cloud/cli/cloud-cli#strapi-deploy), +- or automatically triggered everytime a new commit is pushed to the branch, if the Strapi Cloud project is connected to a git repository and the "deploy on push" option is enabled (see [Project settings](/cloud/projects/settings#modifying-git-repository--branch)). Ongoing deployments can also be [manually cancelled](#cancelling-a-deployment) if needed. diff --git a/docusaurus/docs/cloud/projects/overview.md b/docusaurus/docs/cloud/projects/overview.md index 0eb00b3977..8a114d3f01 100644 --- a/docusaurus/docs/cloud/projects/overview.md +++ b/docusaurus/docs/cloud/projects/overview.md @@ -68,4 +68,3 @@ From the *Overview* tab, you can: - the URL and link to the application - view your project's usage (see [Usage](/cloud/getting-started/usage-billing) for more information) - view your project's latest deploys (see [Deploys](/cloud/projects/deploys) for more information) - diff --git a/docusaurus/docs/cloud/projects/settings.md b/docusaurus/docs/cloud/projects/settings.md index 4d8573d282..e5f8c7a253 100644 --- a/docusaurus/docs/cloud/projects/settings.md +++ b/docusaurus/docs/cloud/projects/settings.md @@ -12,21 +12,30 @@ tags: --- import NotV5 from '/docs/snippets/_not-updated-to-v5.md' +import InvoiceStatus from '/docs/snippets/invoices-statuses.md' # Project settings -From a chosen project's dashboard, the *Settings* tab, located in the header, will redirect you to the *Project Settings* page. It enables you to manage the configurations and settings for your Strapi Cloud project. +From a chosen project's dashboard, the *Settings* tab, located in the header, enables you to manage the configurations and settings for your Strapi Cloud project. -There are 5 tabs available: [*General*](#general), [*Domains*](#domains), [*Backups*](#backups), [*Variables*](#variables) and [*Billing*](#billing). +There are 7 tabs available: + +- ![General icon](/img/assets/icons/Faders.svg) [*General*](#general), +- ![Backups icon](/img/assets/icons/ArrowClockwise.svg) [*Backups*](#backups), +- ![Domains icon](/img/assets/icons/Browsers.svg) [*Domains*](#domains), +- ![Variables icon](/img/assets/icons/code2.svg) [*Variables*](#variables), +- ![Billing & Usage icon](/img/assets/icons/CreditCard.svg) [*Billing & Usage*](#billing--usage), +- ![Plans icon](/img/assets/icons/MapTrifold.svg) [Plans](#plans), +- and ![Invoices icon](/img/assets/icons/Invoice.svg) [Invoices](#invoices). ## General -The *General* tab enables you to check and update the following options for the project: +The ![General icon](/img/assets/icons/Faders.svg) *General* tab enables you to check and update the following options for the project: - *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 [Project creation](/cloud/getting-started/deployment)) and cannot be modified afterwards. -- *Connected Git repository*: to change the branch of the GitHub repository used for your project (see [Modifying GitHub repository branch](#modifying-git-repository-branch)). Also allows to enable/disable the "deploy on push" option. +- *Connected Git repository*: to change the branch of the GitHub repository used for your project (see [Modifying GitHub repository branch](#modifying-git-repository--branch)). Also allows to enable/disable the "deploy on push" option. - *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 [Project creation](/cloud/getting-started/deployment)) and cannot be modified afterwards. - *Debug info*: to see the internal project name for the project. This is useful for support purposes. - *Node version*: to change the Node version of the project (see [Modifying Node version](#modifying-node-version)). @@ -40,16 +49,41 @@ The *General* tab enables you to check and update the following options for the }} /> -### Modifying git repository branch +### Modifying git repository & branch + +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)). After the project's creation, via the project's settings, it is possible to: -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. +- update the project's repository or switch to another git provider (see [Updating repository](#updating-repository)), +- edit the project's branch, base directory and deploy on push setting (see [Editing branch](#editing-branch)). + +:::caution +Updating the git repository could result in the loss of the project and its data, for instance if the wrong repository is selected or if the data schema between the old and new repository doesn't match. +::: -1. In the *Connected git repository* section of the *General* tab, click on the **Edit** button. -2. In the *Edit Git settings* dialog, edit the available options of your choice: +#### Updating repository + +1. In the *Connected git repository* section of the ![General icon](/img/assets/icons/Faders.svg) *General* tab, click on the **Update repository** button. +2. (optional) If you wish to not only update the repository but switch to another git provider, click on the **Switch to GitHub/GitLab** button at the bottom of the *Update repository* dialog. You will be redirected to the chosen git provider's authorization settings before getting back to the *Update repository dialog*. +3. In the *Update repository* dialog, fill in the 3 available settings: | Setting name | Instructions | | --------------- | ------------------------------------------------------------------------ | - | Selected branch | Choose a branch from the drop-down list. | + | Account | Choose an account from the drop-down list. | + | Repository | Choose a repository from the drop-down list. | + | Git branch | Choose a branch from the drop-down list. | + | Deploy the project on every commit pushed to this branch | Tick the box to automatically trigger a new deployment whenever a new commit is pushed to the selected branch. Untick it to disable the option. | + +4. Click on the **Save** button. +5. In the confirmation dialog, confirm your changes by clicking on the **Relink repository** button. + +#### Editing branch + +1. In the *Connected git repository* section of the ![General icon](/img/assets/icons/Faders.svg) *General* tab, click on the **Edit branch** button. +2. In the *Edit branch* dialog, edit the settings below: + + | Setting name | Instructions | + | --------------- | ------------------------------------------------------------------------ | + | Git branch | Choose a branch from the drop-down list. | | Base directory | Write the path of the base directory in the textbox. | | Deploy the project on every commit pushed to this branch | Tick the box to automatically trigger a new deployment whenever a new commit is pushed to the selected branch. Untick it to disable the option. | @@ -59,7 +93,7 @@ The GitHub or Gitlab repository branch and base directory for a Strapi Cloud pro The project's Node version is first chosen at the creation of the project (see [Creating a project](/cloud/getting-started/deployment)), through the advanced settings. It is possible to switch to another Node version afterwards. -1. In the *Node version* section of the *General* tab, click on the **Edit** button. +1. In the *Node version* section of the ![General icon](/img/assets/icons/Faders.svg) *General* tab, click on the **Edit** button. 2. Using the *Node version* drop-down in the dialog, click on the version of your choice. 3. Click on the **Save** button. 4. Click on the **Trigger deploy** button in the right corner of the project's header. If the deployment fails, it is because the Node version doesn't match the version of your Strapi project. You will have to switch to the other Node version and re-deploy your project again. @@ -68,13 +102,57 @@ The project's Node version is first chosen at the creation of the project (see [ You can delete any Strapi Cloud project, but it will be permanent and irreversible. Associated domains, deployments and data will be deleted as well and the subscription for the project will automatically be cancelled. -1. In the *Delete project* section of the *General* tab, click on the **Delete project** button. +1. In the *Delete project* section of the ![General icon](/img/assets/icons/Faders.svg) *General* tab, click on the **Delete project** button. 2. In the dialog, select the reason why you are deleting your project. If selecting "Other" or "Missing feature", a textbox will appear to let you write additional information. 3. Confirm the deletion of your project by clicking on the **Delete project** button at the bottom of the dialog. +## Backups {#backups} + +The ![Backups icon](/img/assets/icons/ArrowClockwise.svg) *Backups* tab informs you of the status and date of the latest backup of your Strapi Cloud projects. The databases associated with all existing Strapi Cloud projects are indeed automatically backed up weekly and those backups are retained for a one-month period. Additionally, you can create a single manual backup. + +:::note Notes + +- The backup feature is not available for Strapi Cloud projects using the free trial or the Developer plan. You will need to upgrade to either the Pro or Team plan to have your project automatically backed up and to have access to manual backups. + +- Only project owners can restore a backup. Maintainers have access to the ![Backups icon](/img/assets/icons/ArrowClockwise.svg) *Backups* tab but the **Restore backup** button won't be displayed for them. Refer to [Collaboration](/cloud/projects/collaboration) for more information. + +- The manual backup option should become available shortly after project's first succesful deployment. + +::: + +:::tip +For projects created before the release of the Backup feature in October 2023, the first backup will automatically be triggered with the next deployment of the project. +::: + + + +### Creating a manual backup + +To create a manual backup, in the ![Backups icon](/img/assets/icons/ArrowClockwise.svg) *Backups* section, click on the **Create backup** button. + +The manual backup should start immediately, and restoration or creation of other backups will be disabled until backup is complete. + +:::caution +When creating a new manual backup, any existing manual backup will be deleted. You can only have one manual backup at a time. +::: + +### Restoring a backup + +If you need to restore a backup of your project: + +1. In the ![Backups icon](/img/assets/icons/ArrowClockwise.svg) *Backups* section, click on the **Restore backup** button. +2. In the dialog, choose one of the available backups (automatic or manual) of your project in the *Choose backup* drop-down. +3. Click on the **Restore** button of the dialog. Once the restoration finished, your project will be back to the state it was at the time of the chosen backup. + ## Domains -The *Domains* tab enables you to manage domains and connect new ones. +The ![Domains icon](/img/assets/icons/Browsers.svg) *Domains* tab enables you to manage domains and connect new ones. -All existing domains for your Strapi Cloud project are listed in the *Domains* tab. For each domain, you can: +All existing domains for your Strapi Cloud project are listed in the ![Domains icon](/img/assets/icons/Browsers.svg) *Domains* tab. For each domain, you can: - see its current status: - ![Edit icon](/img/assets/icons/CheckCircle.svg) Active: the domain is currently confirmed and active @@ -109,71 +187,121 @@ Default domain names are made of 2 randomly generated words followed by a hash. 3. Click on the **Save** button. -## Backups +## Variables -The *Backups* tab informs you of the status and date of the latest backup of your Strapi Cloud projects. The databases associated with all existing Strapi Cloud projects are indeed automatically backed up weekly and those backups are retained for a one-month period. +Environment variables (more information in the [Developer Documentation](../../dev-docs/configurations/environment)) are used to configure the environment of your Strapi application, such as the database connection. -:::note -The backup feature is not available for Strapi Cloud projects using the free trial. You will need to upgrade to either the Pro or Team plan to have your project automatically backed up. + -Note also that only project owners can restore a backup. Maintainers have access to the *Backups* tab but the **Restore backup** button won't be displayed for them. Refer to [Collaboration](/cloud/projects/collaboration) for more information. -::: +In the ![Variables icon](/img/assets/icons/code2.svg) *Variables* tab, you can: +- click the **Add variable** button to create a new variable +- edit any variable, each being composed of a *Name* and a *Value* +- click the ![Delete icon](/img/assets/icons/delete.svg) delete button associated with any variable to delete it +- click the **Save** button to save any change made on the page + +## Billing & Usage + +The ![Billing & Usage icon](/img/assets/icons/CreditCard.svg) *Billing & Usage* tab displays all information on the current subscription plan and included usage for the project, and allows to have a detailed look at the usage. Through this tab, you can also [manage the number of seats for your project](#managing-projects-number-of-seats). :::tip -For projects created before the release of the Backup feature in October 2023, the first backup will automatically be triggered with the next deployment of the project. +In the Usage section of the ![Billing & Usage icon](/img/assets/icons/CreditCard.svg) *Billing & Usage* tab, you can see the current monthly usage of your project compared to the maximum usage allowed by your project's subscription. Use the *Time range* filters to see the project's usage for any chosen month. + +Note also that if your usage indicates that another subscription plan would fit better for your project, a message will be displayed in the ![Billing & Usage icon](/img/assets/icons/CreditCard.svg) *Billing & Usage* tab to advise which plan you could switch to. ::: -### Restoring a backup +### Managing project's number of seats -If you need to restore a backup of your project: +You can manually add more seats or lower the number of seats for your project without necessarily upgrading or downgrading to another plan (see [full documentation on seats management](/cloud/getting-started/usage-billing#seats-management)). -1. In the *Backups* section, click on the **Restore backup** button. -2. In the dialog, choose one of the available backups of your project in the *Choose backup* drop-down. -3. Click on the **Restore** button of the dialog. Once the restoration finished, your project will be back to the state it was at the time of the chosen backup. +#### Adding more seats for the project -## Variables +1. In the ![Billing & Usage icon](/img/assets/icons/CreditCard.svg) *Billing & Usage* tab of your project's settings, click on the **Manage** button next to the displayed number of seats. +2. In the window that opens, select with the drop-down the number of *Additional seats* of your choice. The cost of the additional seats is automatically calculated and displayed in the window. +3. (optional) Click **I have a discount code**, enter your discount code in the field, and click on the **Apply** button. +4. Click the **Save** button to confirm. You will automatically be billed with the payment method defined in your profile. -Environment variables (more information in the [Developer Documentation](../../dev-docs/configurations/environment)) are used to configure the environment of your Strapi application, such as the database connection. +#### Removing seats from the project + +1. In the ![Billing & Usage icon](/img/assets/icons/CreditCard.svg) *Billing & Usage* tab of your project's settings, click on the **Manage** button next to the displayed number of seats. +2. In the window that opens, select with the drop-down the number of *Billed seats* you want to keep. +3. Click the **Save button** to confirm. The new, lower number of seats will not be effective until the next month. + +## Plans + +The ![Plans icon](/img/assets/icons/MapTrifold.svg) *Plans* tab displays an overview of the available Strapi Cloud plans and allows you to upgrade or downgrade from your current plan to another. + +:::note +If you are using the free trial, the *Plan* tab shows a countdown of how many days you have left, as well as indications of the next steps. For more information about the free trial and project suspension, please refer to [Information on billing & usage](/cloud/getting-started/usage-billing). +::: -In the *Variables* tab, you can: -- click the **Add variable** button to create a new variable -- edit any variable, each being composed of a *Name* and a *Value* -- click the ![Delete icon](/img/assets/icons/delete.svg) delete button associated with any variable to delete it -- click the **Save** button to save any change made on the page +### Upgrading to another plan + +Strapi Cloud plan upgrades to another, higher plan are immediate and can be managed for each project via the project settings. + +:::note +When using the free trial, the buttons to upgrade to another plan are greyed out and unusable until you have filled in your billing information. Please refer to [Account billing details](/cloud/account/account-billing) for more information. +::: -## Billing +To upgrade your current plan to a higher one: -The *Billing* tab displays all information on the current subscription plan and included usage for the project. Through this tab, you can [manage the subscription of your project](#managing-projects-subscription) and have a detailed look at its usage. +1. In the ![Plans icon](/img/assets/icons/MapTrifold.svg) *Plans* tab of your project's settings, click on the **Upgrade** button of the plan you want to upgrade to. +2. In the window that opens, check the payment details that indicate how much you will have to pay immediately after confirming the upgrade, and the available options. -:::tip -In the Usage section of the *Billing* tab, you can see the current monthly usage of your project compared to the maximum usage allowed by your project's subscription. Use the *Time range* filters to see the project's usage for any chosen month. + a. (optional) Click the **Edit** button to select another payment method. + b. (optional) Click **I have a discount code**, enter your discount code in the field, and click on the **Apply** button. + +3. Click on the **Upgrade to [plan name]** button to confirm the upgrade of your Strapi project to another plan. + +### Downgrading to another plan + +Strapi Cloud plan downgrades can be managed for each project via the project settings. Downgrades are however not immediately effective: the higher plan will still remain active until the end of the current month (e.g. if you downgrade from the Team plan to the Pro plan on June 18th, your project will remain on the Team plan until the end of the month: on July 1st, the Pro plan will be effective for the project). + +:::caution +Make sure to check the usage of your Strapi Cloud project before downgrading: if your current usage exceeds the limits of the lower plan, you are taking the risk of getting charged for the overages. Note also that you may lose access to some features: for example, downgrading to the Developer plan which doesn't include the Backups feature, would make you lose all your project's backups. Please refer to [Information on billing & usage](/cloud/getting-started/usage-billing) for more information. ::: +To downgrade your current plan to a lower one: + +1. In the ![Plans icon](/img/assets/icons/MapTrifold.svg) *Plans* tab of your project's settings, click on the **Downgrade** button of the plan you want to downgrade to. +2. In the window that opens, check the information related to downgrading. +3. Click on the **Downgrade** button to confirm the downgrade of your Strapi project's plan. + +## Invoices + +The ![Invoices icon](/img/assets/icons/Invoice.svg) *Invoices* tab displays the full list of invoices for your Strapi Cloud project as well as their status. + -### Managing project's subscription + -Using the **Manage subscriptions** button, you can view and manage your project's subscription. Please refer to [Account management > Account billing details](/cloud/account/account-billing) for the full documentation of the subscription management modal. - \ No newline at end of file +:::strapi Invoices are also available in your profile settings. +In the *Profile > Invoices* tab, you will find the complete list of invoices for all your projects. Feel free to check the [dedicated documentation](/cloud/account/account-billing#account-invoices). +::: diff --git a/docusaurus/docs/snippets/invoices-statuses.md b/docusaurus/docs/snippets/invoices-statuses.md new file mode 100644 index 0000000000..8d3aac62e3 --- /dev/null +++ b/docusaurus/docs/snippets/invoices-statuses.md @@ -0,0 +1,11 @@ +Invoices can have any of the following statuses: + +- Paid: the payment has been done and the invoice is available, no additional action is required. +- Payment pending: the invoice is not complete or validated yet +- Payment due: the paiement didn't go through and needs to be fixed +- Not paid: the payment has failed and won't automatically be retried +- Voided: the invoice has been cancelled. + +:::tip +Click the ![download icon](/img/assets/icons/download.svg) icon to download an invoice. +::: \ No newline at end of file diff --git a/docusaurus/static/img/assets/cloud/account-billing2.png b/docusaurus/static/img/assets/cloud/account-billing2.png index 7238c7bb88..97bc5f55cb 100644 Binary files a/docusaurus/static/img/assets/cloud/account-billing2.png and b/docusaurus/static/img/assets/cloud/account-billing2.png differ diff --git a/docusaurus/static/img/assets/cloud/account-billing2_DARK.png b/docusaurus/static/img/assets/cloud/account-billing2_DARK.png index e92f616153..e637e41649 100644 Binary files a/docusaurus/static/img/assets/cloud/account-billing2_DARK.png and b/docusaurus/static/img/assets/cloud/account-billing2_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/account-invoices.png b/docusaurus/static/img/assets/cloud/account-invoices.png new file mode 100644 index 0000000000..954850f390 Binary files /dev/null and b/docusaurus/static/img/assets/cloud/account-invoices.png differ diff --git a/docusaurus/static/img/assets/cloud/account-invoices_DARK.png b/docusaurus/static/img/assets/cloud/account-invoices_DARK.png new file mode 100644 index 0000000000..cf6153b7bd Binary files /dev/null and b/docusaurus/static/img/assets/cloud/account-invoices_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/account-preferences.png b/docusaurus/static/img/assets/cloud/account-preferences.png index 4891702021..f307acd302 100644 Binary files a/docusaurus/static/img/assets/cloud/account-preferences.png and b/docusaurus/static/img/assets/cloud/account-preferences.png differ diff --git a/docusaurus/static/img/assets/cloud/account-preferences_DARK.png b/docusaurus/static/img/assets/cloud/account-preferences_DARK.png index fe6bbcfd51..3a3da0b180 100644 Binary files a/docusaurus/static/img/assets/cloud/account-preferences_DARK.png and b/docusaurus/static/img/assets/cloud/account-preferences_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/login.png b/docusaurus/static/img/assets/cloud/login.png index 1b1aa0e148..4e0a8e2a92 100644 Binary files a/docusaurus/static/img/assets/cloud/login.png and b/docusaurus/static/img/assets/cloud/login.png differ diff --git a/docusaurus/static/img/assets/cloud/login_DARK.png b/docusaurus/static/img/assets/cloud/login_DARK.png index 28dfcb243f..9cfaf20a7b 100644 Binary files a/docusaurus/static/img/assets/cloud/login_DARK.png and b/docusaurus/static/img/assets/cloud/login_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/project-creation-1.png b/docusaurus/static/img/assets/cloud/project-creation-1.png index bef755e94b..deafa9ec65 100644 Binary files a/docusaurus/static/img/assets/cloud/project-creation-1.png and b/docusaurus/static/img/assets/cloud/project-creation-1.png differ diff --git a/docusaurus/static/img/assets/cloud/project-creation-1_DARK.png b/docusaurus/static/img/assets/cloud/project-creation-1_DARK.png index aa6d1277c2..fe1b2d4648 100644 Binary files a/docusaurus/static/img/assets/cloud/project-creation-1_DARK.png and b/docusaurus/static/img/assets/cloud/project-creation-1_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/settings-general.png b/docusaurus/static/img/assets/cloud/settings-general.png index 3e8961d4c2..9e10563822 100644 Binary files a/docusaurus/static/img/assets/cloud/settings-general.png and b/docusaurus/static/img/assets/cloud/settings-general.png differ diff --git a/docusaurus/static/img/assets/cloud/settings-general_DARK.png b/docusaurus/static/img/assets/cloud/settings-general_DARK.png index 4b4564bfb0..65b582df93 100644 Binary files a/docusaurus/static/img/assets/cloud/settings-general_DARK.png and b/docusaurus/static/img/assets/cloud/settings-general_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/settings.png b/docusaurus/static/img/assets/cloud/settings.png index eec1ea1310..38070e1e68 100644 Binary files a/docusaurus/static/img/assets/cloud/settings.png and b/docusaurus/static/img/assets/cloud/settings.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_DARK.png b/docusaurus/static/img/assets/cloud/settings_DARK.png index 3db40e8db2..dc0798f7ad 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_DARK.png and b/docusaurus/static/img/assets/cloud/settings_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_backups.png b/docusaurus/static/img/assets/cloud/settings_backups.png index 844aa39eec..f3d7e2e900 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_backups.png and b/docusaurus/static/img/assets/cloud/settings_backups.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_backups_DARK.png b/docusaurus/static/img/assets/cloud/settings_backups_DARK.png index 4300766c71..e2a94257d3 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_backups_DARK.png and b/docusaurus/static/img/assets/cloud/settings_backups_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_billing.png b/docusaurus/static/img/assets/cloud/settings_billing.png index cb4aa6f483..ad18b60417 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_billing.png and b/docusaurus/static/img/assets/cloud/settings_billing.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_billing_DARK.png b/docusaurus/static/img/assets/cloud/settings_billing_DARK.png index acef5caa34..aa46bb2da6 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_billing_DARK.png and b/docusaurus/static/img/assets/cloud/settings_billing_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_domains.png b/docusaurus/static/img/assets/cloud/settings_domains.png index 7920190389..765f583f2a 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_domains.png and b/docusaurus/static/img/assets/cloud/settings_domains.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_domains_DARK.png b/docusaurus/static/img/assets/cloud/settings_domains_DARK.png index 62b3a92051..7ff835e012 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_domains_DARK.png and b/docusaurus/static/img/assets/cloud/settings_domains_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_invoices.png b/docusaurus/static/img/assets/cloud/settings_invoices.png new file mode 100644 index 0000000000..2a66109438 Binary files /dev/null and b/docusaurus/static/img/assets/cloud/settings_invoices.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_invoices_DARK.png b/docusaurus/static/img/assets/cloud/settings_invoices_DARK.png new file mode 100644 index 0000000000..ee6c83f9db Binary files /dev/null and b/docusaurus/static/img/assets/cloud/settings_invoices_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_plans.png b/docusaurus/static/img/assets/cloud/settings_plans.png new file mode 100644 index 0000000000..d3c6444c0c Binary files /dev/null and b/docusaurus/static/img/assets/cloud/settings_plans.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_plans_DARK.png b/docusaurus/static/img/assets/cloud/settings_plans_DARK.png new file mode 100644 index 0000000000..6ed9b6c362 Binary files /dev/null and b/docusaurus/static/img/assets/cloud/settings_plans_DARK.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_variables.png b/docusaurus/static/img/assets/cloud/settings_variables.png index a15225cdb3..cdf0cd6dcf 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_variables.png and b/docusaurus/static/img/assets/cloud/settings_variables.png differ diff --git a/docusaurus/static/img/assets/cloud/settings_variables_DARK.png b/docusaurus/static/img/assets/cloud/settings_variables_DARK.png index 78f0582d71..8e86b6b7d6 100644 Binary files a/docusaurus/static/img/assets/cloud/settings_variables_DARK.png and b/docusaurus/static/img/assets/cloud/settings_variables_DARK.png differ diff --git a/docusaurus/static/img/assets/icons/ArrowClockwise.svg b/docusaurus/static/img/assets/icons/ArrowClockwise.svg new file mode 100644 index 0000000000..4a92e6a522 --- /dev/null +++ b/docusaurus/static/img/assets/icons/ArrowClockwise.svg @@ -0,0 +1,3 @@ + + + diff --git a/docusaurus/static/img/assets/icons/Browsers.svg b/docusaurus/static/img/assets/icons/Browsers.svg new file mode 100644 index 0000000000..de61260875 --- /dev/null +++ b/docusaurus/static/img/assets/icons/Browsers.svg @@ -0,0 +1,3 @@ + + + diff --git a/docusaurus/static/img/assets/icons/CreditCard.svg b/docusaurus/static/img/assets/icons/CreditCard.svg new file mode 100644 index 0000000000..36db6c2f77 --- /dev/null +++ b/docusaurus/static/img/assets/icons/CreditCard.svg @@ -0,0 +1,3 @@ + + + diff --git a/docusaurus/static/img/assets/icons/Faders.svg b/docusaurus/static/img/assets/icons/Faders.svg new file mode 100644 index 0000000000..de08c1a0ba --- /dev/null +++ b/docusaurus/static/img/assets/icons/Faders.svg @@ -0,0 +1,3 @@ + + + diff --git a/docusaurus/static/img/assets/icons/Invoice.svg b/docusaurus/static/img/assets/icons/Invoice.svg new file mode 100644 index 0000000000..f5b9188fed --- /dev/null +++ b/docusaurus/static/img/assets/icons/Invoice.svg @@ -0,0 +1,3 @@ + + + diff --git a/docusaurus/static/img/assets/icons/MapTrifold.svg b/docusaurus/static/img/assets/icons/MapTrifold.svg new file mode 100644 index 0000000000..ce6cc00215 --- /dev/null +++ b/docusaurus/static/img/assets/icons/MapTrifold.svg @@ -0,0 +1,3 @@ + + + diff --git a/docusaurus/static/img/assets/icons/Palette.svg b/docusaurus/static/img/assets/icons/Palette.svg new file mode 100644 index 0000000000..e98e082e9d --- /dev/null +++ b/docusaurus/static/img/assets/icons/Palette.svg @@ -0,0 +1,3 @@ + + + diff --git a/docusaurus/static/img/assets/icons/code2.svg b/docusaurus/static/img/assets/icons/code2.svg new file mode 100644 index 0000000000..8f9735d5dd --- /dev/null +++ b/docusaurus/static/img/assets/icons/code2.svg @@ -0,0 +1,3 @@ + + +