From ff8cf304b6547fe4faba0f60cacff76ceca77ce6 Mon Sep 17 00:00:00 2001 From: Stephane Le Choisnier Date: Thu, 31 Jul 2025 14:57:47 +0200 Subject: [PATCH 01/39] [ STORY-2130] Added section about projects management and details about change of project and project choice during app creation --- src/_posts/platform/2000-01-01-cli.md | 2 +- src/_posts/platform/2000-01-01-projects.md | 4 ++ .../projects/2000-01-01-manage-projects.md | 63 +++++++++++++++++++ 3 files changed, 68 insertions(+), 1 deletion(-) create mode 100644 src/_posts/platform/2000-01-01-projects.md create mode 100644 src/_posts/platform/projects/2000-01-01-manage-projects.md diff --git a/src/_posts/platform/2000-01-01-cli.md b/src/_posts/platform/2000-01-01-cli.md index 2e7ff6c3d..7ba4030e7 100644 --- a/src/_posts/platform/2000-01-01-cli.md +++ b/src/_posts/platform/2000-01-01-cli.md @@ -1,4 +1,4 @@ --- title: CLI -index: 5 +index: 6 --- diff --git a/src/_posts/platform/2000-01-01-projects.md b/src/_posts/platform/2000-01-01-projects.md new file mode 100644 index 000000000..ebae6994a --- /dev/null +++ b/src/_posts/platform/2000-01-01-projects.md @@ -0,0 +1,4 @@ +--- +title: Projects +index: 5 +--- \ No newline at end of file diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md new file mode 100644 index 000000000..a6f9fb000 --- /dev/null +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -0,0 +1,63 @@ +--- +title: Manage your projects +modified_at: 2025-07-31 07:00:00 +tags: project management +index: 1 +--- + +## Introduction + +Projects help to structure your resources by gathering them. They're the first milestone of features that will come later like network isolation for instance. + +The project named **⭐ default** is present by default and is set as a default project on existing Apps. + +{% note %} +You're encouraged to assign your apps to projects now. +By doing this, you prepare the arrival of some of the future features, that in the end will make the gathering of resources per projects necessary. +{% endnote %} + +## Setting the project at App creation + +### Using the Dashboard + +Within the App creation wizard, the section **Project** enables you to set a project different from **⭐ default**. + +If the project you'd like to set against the new App, doesn't exist, proceed as follow: + +1. Click **+ New project** +2. Enter the project name of your choice (only characters a-Z 0-9 - _ are allowed) +3. Click **Add** + +If the project is in the list +1. Select the project you want +2. Proceed with the next steps of your app creation + + +## Updating the project of an existing App + +### Using the Dashboard + +1. From your web browser, open your [dashboard][dashboard] +2. Click the **Apps** tab +3. Click on the application for which you want to manage the project +4. Click the **Settings** tab +5. In the **Settings** submenu, make sure to select **App management** +6. In the section **Parent project**, click **Move app to another project** + + +If the project isn't already existing, proceed as follow: + +1. Click **+ New project** +2. Enter the project name of your choice (only characters a-Z 0-9 - _ are allowed) +3. Click **Add** + + +If the project is in the list + +1. Select the project you want +2. Click **Move app to project** + + + + +[dashboard]: https://dashboard.scalingo.com/ \ No newline at end of file From 6a31e9305910baf243793eed9874229d1e3fa317 Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Tue, 5 Aug 2025 11:46:59 +0200 Subject: [PATCH 02/39] Update documentation for projects within application management --- .../projects/2000-01-01-manage-projects.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index a6f9fb000..88f3f0b66 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -32,6 +32,13 @@ If the project is in the list 1. Select the project you want 2. Proceed with the next steps of your app creation +### Using the Command Line + +This feature is not yet available in the CLI. + +### Using the Terraform Provider + +This feature is not yet available in the Terraform Provider. ## Updating the project of an existing App @@ -57,7 +64,15 @@ If the project is in the list 1. Select the project you want 2. Click **Move app to project** +### Using the Command Line + +This feature is not yet available in the CLI. + +### Using the Terraform Provider + +This feature is not yet available in the Terraform Provider. +[dashboard]: https://dashboard.scalingo.com/ -[dashboard]: https://dashboard.scalingo.com/ \ No newline at end of file +[cli]: {% post_url platform/cli/2000-01-01-start %} \ No newline at end of file From b5aee876477ace057c0ebecf454a9806cbc67dd5 Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Tue, 5 Aug 2025 12:37:44 +0200 Subject: [PATCH 03/39] Add project creation --- .../projects/2000-01-01-manage-projects.md | 31 +++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 88f3f0b66..1ef97bbcd 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -72,6 +72,37 @@ This feature is not yet available in the CLI. This feature is not yet available in the Terraform Provider. +## Creating a new project + +### Using the Dashboard + +Right now it is only possible to create a new project when creating a new application. + +### Using the Command Line + +1. Make sure you have correctly [setup the Scalingo command line tool][cli] +2. From the command line, create a project: + ```shell + scalingo projects-add test-project + ``` + The output should look like this: + ```text + -----> test-project has been created + ``` + You can also create a new project that will be default directly: + ```shell + scalingo projects-add --default test-project + ``` + +### Using the Terraform Provider + +1. Place the following `resource` block in your Terraform file: + ```tf + resource "scalingo_project" "test-project" { + name = "test-project" + default = true + } + ``` [dashboard]: https://dashboard.scalingo.com/ From bacc168da4c5225f0d0909fab7bbbf66f27759cd Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Tue, 5 Aug 2025 12:43:27 +0200 Subject: [PATCH 04/39] Add project listing --- .../projects/2000-01-01-manage-projects.md | 30 ++++++++++++++++++- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 1ef97bbcd..ee9b3db03 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -72,6 +72,34 @@ This feature is not yet available in the CLI. This feature is not yet available in the Terraform Provider. +## Listing the projects + +{% warning %} +For the moment, listing the projects will return only projects where you are the owner. +{% endwarning %} + +### Using the Dashboard + +Right now it is only possible to list the projects when creating a new application. + +### Using the Command Line + +1. Make sure you have correctly [setup the Scalingo command line tool][cli] +2. From the command line, list the projects: + ```shell + scalingo projects + ``` + The output should look like this: + ```shell + /!\ This command only displays projects where you are the owner + ┌──────────────┬─────────┬──────────────────────────────────────────┐ + │ NAME │ DEFAULT │ ID │ + ├──────────────┼─────────┼──────────────────────────────────────────┤ + │ test-project │ false │ prj-6631a609-02b6-4614-b28d-5abe436543d3 │ + │ default │ true │ prj-29f1b7e4-cf4d-46e9-aff1-e47ae149c486 │ + └──────────────┴─────────┴──────────────────────────────────────────┘ + ``` + ## Creating a new project ### Using the Dashboard @@ -86,7 +114,7 @@ Right now it is only possible to create a new project when creating a new applic scalingo projects-add test-project ``` The output should look like this: - ```text + ```shell -----> test-project has been created ``` You can also create a new project that will be default directly: From a9895b449c41cd2302742366a870ffbbcefd167c Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Tue, 5 Aug 2025 12:53:51 +0200 Subject: [PATCH 05/39] Add project update --- .../projects/2000-01-01-manage-projects.md | 36 +++++++++++++++++-- 1 file changed, 34 insertions(+), 2 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index ee9b3db03..195a08b8e 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -95,8 +95,8 @@ Right now it is only possible to list the projects when creating a new applicati ┌──────────────┬─────────┬──────────────────────────────────────────┐ │ NAME │ DEFAULT │ ID │ ├──────────────┼─────────┼──────────────────────────────────────────┤ - │ test-project │ false │ prj-6631a609-02b6-4614-b28d-5abe436543d3 │ - │ default │ true │ prj-29f1b7e4-cf4d-46e9-aff1-e47ae149c486 │ + │ test-project │ false │ prj-6731a609-02b6-4614-b28d-5abe43654333 │ + │ default │ true │ prj-20f1b7e4-cf4d-46e9-aff1-e47ae149c444 │ └──────────────┴─────────┴──────────────────────────────────────────┘ ``` @@ -132,6 +132,38 @@ Right now it is only possible to create a new project when creating a new applic } ``` +## Updating a project + +Two attributes can be updated: `name` and `default`. + +{% note %} + `default` cannot be changed from true to false. To change the default project, update an existing project to be the new default one, or create a new default project. +{% endnote %} + +### Using the Dashboard + +This feature is not yet available in the dashboard. + +### Using the Command Line + +1. Make sure you have correctly [setup the Scalingo command line tool][cli] +2. From the command line, update a project: + ```shell + scalingo projects-update --name=updated-test-project prj-6731a609-02b6-4614-b28d-5abe43654333 + ``` + The output should look like this: + ```shell + -----> test-project has been updated + ``` + You can also update a project to become the new default: + ```shell + scalingo projects-update --default prj-6731a609-02b6-4614-b28d-5abe43654333 + ``` + +### Using the Terraform Provider + +1. The only thing to do is update the project `resource` with a new `name` or `default` attribute. + [dashboard]: https://dashboard.scalingo.com/ [cli]: {% post_url platform/cli/2000-01-01-start %} \ No newline at end of file From f78bee0561c7542355db4c081b8b14a24eaabea2 Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Tue, 5 Aug 2025 12:59:24 +0200 Subject: [PATCH 06/39] Improve project update --- .../platform/projects/2000-01-01-manage-projects.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 195a08b8e..8efa8946e 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -162,7 +162,13 @@ This feature is not yet available in the dashboard. ### Using the Terraform Provider -1. The only thing to do is update the project `resource` with a new `name` or `default` attribute. +There is only one step required to update a project using Terraform. You need to +update the project with the desired attributes. For example: + ```tf + resource "scalingo_project" "test-project" { + name = "updated-test-project" + } + ``` [dashboard]: https://dashboard.scalingo.com/ From 43c61de1dc11a8713eecc2b2793874effedf868c Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Tue, 5 Aug 2025 15:21:24 +0200 Subject: [PATCH 07/39] Add project removal --- .../projects/2000-01-01-manage-projects.md | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 8efa8946e..476b8bcf3 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -52,7 +52,7 @@ This feature is not yet available in the Terraform Provider. 6. In the section **Parent project**, click **Move app to another project** -If the project isn't already existing, proceed as follow: +If the project isn't already existing, proceed as follows: 1. Click **+ New project** 2. Enter the project name of your choice (only characters a-Z 0-9 - _ are allowed) @@ -170,6 +170,31 @@ update the project with the desired attributes. For example: } ``` +## Removing a project + +A project can be removed only if this is not the default one, and no application is linked to it. + +### Using the Dashboard + +This feature is not yet available in the dashboard. + +### Using the Command Line + +1. Make sure you have correctly [setup the Scalingo command line tool][cli] +2. From the command line, update a project: + ```shell + scalingo projects-remove prj-6731a609-02b6-4614-b28d-5abe43654333 + ``` + The output should look like this: + ```shell + -----> prj-6731a609-02b6-4614-b28d-5abe43654333 has been removed + ``` + +### Using the Terraform Provider + +There is only one step required to remove a project using Terraform. You just need to +remove the associated resource from the Terraform file. + [dashboard]: https://dashboard.scalingo.com/ [cli]: {% post_url platform/cli/2000-01-01-start %} \ No newline at end of file From e51aa092b865251584e2e691a4c8bc65cf86f42d Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Tue, 5 Aug 2025 15:27:25 +0200 Subject: [PATCH 08/39] Mention STORY-2326 for tracking --- src/_posts/platform/projects/2000-01-01-manage-projects.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 476b8bcf3..eb76c6b1a 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -22,7 +22,7 @@ By doing this, you prepare the arrival of some of the future features, that in t Within the App creation wizard, the section **Project** enables you to set a project different from **⭐ default**. -If the project you'd like to set against the new App, doesn't exist, proceed as follow: +If the project you'd like to set against the new App, doesn't exist, proceed as follows: 1. Click **+ New project** 2. Enter the project name of your choice (only characters a-Z 0-9 - _ are allowed) From 021a993f08de353ba9256a17ef10bc80d074a350 Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Wed, 6 Aug 2025 14:55:12 +0200 Subject: [PATCH 09/39] Update documentation for app creation --- .../platform/projects/2000-01-01-manage-projects.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index eb76c6b1a..578533d63 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -34,7 +34,17 @@ If the project is in the list ### Using the Command Line -This feature is not yet available in the CLI. +1. Make sure you have correctly [setup the Scalingo command line tool][cli] +2. From the command line, list the projects: + ```shell + scalingo create --project-id=prj-6731a609-02b6-4614-b28d-5abe43654333 test-app + ``` + The output should look like this: + ```shell + App 'test-app' has been created + To deploy your application, run these commands in your GIT repository: + ... + ``` ### Using the Terraform Provider From a050e087df6126123da234f54e7046d1dbcf05a8 Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Wed, 6 Aug 2025 14:56:39 +0200 Subject: [PATCH 10/39] Also update the lifecycle page --- src/_posts/platform/app/2000-01-01-lifecycle-management.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/_posts/platform/app/2000-01-01-lifecycle-management.md b/src/_posts/platform/app/2000-01-01-lifecycle-management.md index 14cf677cd..c2029a675 100644 --- a/src/_posts/platform/app/2000-01-01-lifecycle-management.md +++ b/src/_posts/platform/app/2000-01-01-lifecycle-management.md @@ -45,6 +45,9 @@ $ scalingo create my-app --remote staging # Create a new app with a custom buildpack $ scalingo create my-app --buildpack https://github.com/Scalingo/multi-buildpack + +# Create a new app in the chosen project +$ scalingo create --project-id=prj-6731a609-02b6-4614-b28d-5abe43654333 my-app ``` ## Rename an Application From 96bdb4367807745a2347849f1eb467b2405c460a Mon Sep 17 00:00:00 2001 From: Matthieu Bronner Date: Thu, 7 Aug 2025 09:57:36 +0200 Subject: [PATCH 11/39] Improve doc for app creation in Terraform --- .../platform/projects/2000-01-01-manage-projects.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 578533d63..0fd0ba3a7 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -48,7 +48,13 @@ If the project is in the list ### Using the Terraform Provider -This feature is not yet available in the Terraform Provider. +1. Place the following `project_id` in the app `resource` block in your Terraform file: + ```tf + resource "scalingo_app" "test_app" { + name = "terraform-testapp" + project_id = "prj-6731a609-02b6-4614-b28d-5abe43654333" + } + ``` ## Updating the project of an existing App From 474a401090a8bd24284f4505e0bf8ca932f21d81 Mon Sep 17 00:00:00 2001 From: Stephane Le Choisnier Date: Wed, 27 Aug 2025 09:39:18 +0200 Subject: [PATCH 12/39] Fixed section about setting the project at app creation with command line. Little changes to make more precise some steps --- .../projects/2000-01-01-manage-projects.md | 24 ++++++++++++++++--- 1 file changed, 21 insertions(+), 3 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 0fd0ba3a7..d29af9ae3 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -37,7 +37,24 @@ If the project is in the list 1. Make sure you have correctly [setup the Scalingo command line tool][cli] 2. From the command line, list the projects: ```shell - scalingo create --project-id=prj-6731a609-02b6-4614-b28d-5abe43654333 test-app + scalingo projects + ``` + The output should look like this: + ```shell + /!\ This command only displays projects where you are the owner + ┌─────────────────────────────┬──────────┬─────────────────────────────────┐ + │ NAME │ DEFAULT │ ID │ + ├─────────────────────────────┼──────────┼─────────────────────────────────┤ + │ project_boo │ false │ prj-0c1ab18c-6ac8-4f85-b55e-b14 │ + │ projectBar │ false │ prj-0c1ab74c-6ac8-7k125-b5e-b7 │ + | default │ true │ prj-0c1adc1c-1ad8-4f85-b55e-z9 │ + └─────────────────────────────┴──────────┴─────────────────────────────────┘ + ``` + +3. From the command line, set the project at the app creation step: + + ```shell + scalingo create --project-id=prj-6731a609-02b6-4614-b28d test-app ``` The output should look like this: ```shell @@ -45,6 +62,7 @@ If the project is in the list To deploy your application, run these commands in your GIT repository: ... ``` +Here you've created the App named `test-app` and set the project, which id is `prj-6731a609-02b6-4614-b28d`, on it ### Using the Terraform Provider @@ -120,7 +138,7 @@ Right now it is only possible to list the projects when creating a new applicati ### Using the Dashboard -Right now it is only possible to create a new project when creating a new application. +Right now it is only possible to create a new project when creating a new application or when moving an existing application to another project. ### Using the Command Line @@ -163,7 +181,7 @@ This feature is not yet available in the dashboard. ### Using the Command Line 1. Make sure you have correctly [setup the Scalingo command line tool][cli] -2. From the command line, update a project: +2. From the command line, update a project name: ```shell scalingo projects-update --name=updated-test-project prj-6731a609-02b6-4614-b28d-5abe43654333 ``` From 31d9c8b5206da9a94d632b7180d93439eabab329 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Fri, 29 Aug 2025 17:38:41 +0200 Subject: [PATCH 13/39] Creation of an overview page where we can introduce projects more broadly, while keeping the existing page for technical details. --- .../projects/2000-01-01-manage-projects.md | 4 +-- .../platform/projects/2000-01-01-overview.md | 31 +++++++++++++++++++ 2 files changed, 33 insertions(+), 2 deletions(-) create mode 100644 src/_posts/platform/projects/2000-01-01-overview.md diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index d29af9ae3..3c8ee71de 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -1,8 +1,8 @@ --- title: Manage your projects -modified_at: 2025-07-31 07:00:00 +modified_at: 2025-08-29 07:00:00 tags: project management -index: 1 +index: 2 --- ## Introduction diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md new file mode 100644 index 000000000..bb2da323a --- /dev/null +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -0,0 +1,31 @@ +--- +title: Manage your projects +modified_at: 2025-08-29 07:00:00 +tags: project overview +index: 1 +--- + +Projects offer a new way to organize your applications. By grouping your resources into projects now, you are preparing for upcoming features focused on the network isolation of your applications and environments. + +{% note %} +We encourage you to group your applications into projects now. +This will prepare you for upcoming features (such as private networks) and ensure smooth transition, as moving applications between projects will eventually require downtime. +{% endnote %} + +## Why use Projects? + +Projects provide a structured way to separate applications according to your own logic, +whether by product, customer, environment, or any other approach that fits your needs. This makes large accounts easier to navigate and manage, while keeping resources clearly organized. + +In the near future, Projects will become the cornerstone for application billing, security, and network isolation. While these advanced features are not yet available, introducing Projects today gives you the opportunity to start aligning your applications with this organizational model. By grouping your apps into Projects now, you will be better prepared to take full advantage of these upcoming capabilities. + +## Default Project + +Every owner starts with a Project named default, which serves as the initial workspace. This Project can be renamed at any time to better reflect the organization’s needs. + +## Current Limitations + +- Currently, only the owner of a project or an app can move an application between projects. +- Projects cannot be deleted from the Dashboard, they can only be removed using the CLI or API. +- Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. +- Accounts are limited to 100 projects to prevent abuse. This limit can be raised depending on your needs by contacting our support team. From 7a019c89b024bd26de393b753ca29a2107a113db Mon Sep 17 00:00:00 2001 From: Benjamin Date: Fri, 29 Aug 2025 17:47:13 +0200 Subject: [PATCH 14/39] Add links between pages --- src/_posts/platform/projects/2000-01-01-overview.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index bb2da323a..30f1a350d 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -12,6 +12,8 @@ We encourage you to group your applications into projects now. This will prepare you for upcoming features (such as private networks) and ensure smooth transition, as moving applications between projects will eventually require downtime. {% endnote %} +[**Learn how to manage your projects**][project-management-page]. + ## Why use Projects? Projects provide a structured way to separate applications according to your own logic, @@ -26,6 +28,9 @@ Every owner starts with a Project named default, which serves as the initial wor ## Current Limitations - Currently, only the owner of a project or an app can move an application between projects. -- Projects cannot be deleted from the Dashboard, they can only be removed using the CLI or API. +- Projects cannot be deleted from the Dashboard, they can only be [removed using the CLI or API][removing-project]. - Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. - Accounts are limited to 100 projects to prevent abuse. This limit can be raised depending on your needs by contacting our support team. + +[project-management-page]: {% post_url platform/projects/2000-01-01-manage-projects %} +[removing-project]: {% post_url platform/projects/2000-01-01-manage-projects %}#removing-a-project From 5c96d31eee830e923551f66d5f76ca163d9cd429 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Fri, 29 Aug 2025 17:48:27 +0200 Subject: [PATCH 15/39] Update page title --- src/_posts/platform/projects/2000-01-01-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index 30f1a350d..c8b1cecfa 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -1,5 +1,5 @@ --- -title: Manage your projects +title: Projects Overview modified_at: 2025-08-29 07:00:00 tags: project overview index: 1 From ad6adb689bc92ef513f184146547e0931373017a Mon Sep 17 00:00:00 2001 From: Benjamin Date: Fri, 29 Aug 2025 17:58:38 +0200 Subject: [PATCH 16/39] Apply suggestions from code review --- .../platform/projects/2000-01-01-manage-projects.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 3c8ee71de..934b6d020 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -7,13 +7,13 @@ index: 2 ## Introduction -Projects help to structure your resources by gathering them. They're the first milestone of features that will come later like network isolation for instance. +Projects offer a new way to organize your applications. By grouping them into projects now, you are preparing for upcoming features focused on the network isolation of your applications and environments. The project named **⭐ default** is present by default and is set as a default project on existing Apps. {% note %} -You're encouraged to assign your apps to projects now. -By doing this, you prepare the arrival of some of the future features, that in the end will make the gathering of resources per projects necessary. +We encourage you to group your applications into projects now. +This will prepare you for upcoming features (such as private networks) and ensure smooth transition, as moving applications between projects will eventually require downtime. {% endnote %} ## Setting the project at App creation @@ -109,7 +109,7 @@ This feature is not yet available in the Terraform Provider. ## Listing the projects {% warning %} -For the moment, listing the projects will return only projects where you are the owner. +For the moment, listing projects will only return those where you are the owner. {% endwarning %} ### Using the Dashboard From 38c99f92468cad2343ffe71e4bc6ec777a66040e Mon Sep 17 00:00:00 2001 From: Benjamin Date: Fri, 29 Aug 2025 18:17:06 +0200 Subject: [PATCH 17/39] Reorganize information between the two pages. --- .../projects/2000-01-01-manage-projects.md | 16 +++++++++------- .../platform/projects/2000-01-01-overview.md | 4 ++-- 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 934b6d020..ec6b57935 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -1,5 +1,5 @@ --- -title: Manage your projects +title: Manage your Projects modified_at: 2025-08-29 07:00:00 tags: project management index: 2 @@ -7,20 +7,21 @@ index: 2 ## Introduction -Projects offer a new way to organize your applications. By grouping them into projects now, you are preparing for upcoming features focused on the network isolation of your applications and environments. +Projects offer a new way to organize your applications. -The project named **⭐ default** is present by default and is set as a default project on existing Apps. +All existing resources have been assigned to a project named **default**. You can rename this project or move resources to another project at any time. {% note %} -We encourage you to group your applications into projects now. -This will prepare you for upcoming features (such as private networks) and ensure smooth transition, as moving applications between projects will eventually require downtime. +Grouping your applications into projects now will ease the transition to upcoming features and avoid downtime when moving applications later. {% endnote %} +[Learn more about Projects][[projects-overview]. + ## Setting the project at App creation ### Using the Dashboard -Within the App creation wizard, the section **Project** enables you to set a project different from **⭐ default**. +Within the App creation wizard, the section **Project** enables you to set a project different from **default**. If the project you'd like to set against the new App, doesn't exist, proceed as follows: @@ -231,4 +232,5 @@ remove the associated resource from the Terraform file. [dashboard]: https://dashboard.scalingo.com/ -[cli]: {% post_url platform/cli/2000-01-01-start %} \ No newline at end of file +[cli]: {% post_url platform/cli/2000-01-01-start %} +[projects-overview]: {% post_url platform/projects/2000-01-01-overview %} \ No newline at end of file diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index c8b1cecfa..a8cf45fb3 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -12,7 +12,7 @@ We encourage you to group your applications into projects now. This will prepare you for upcoming features (such as private networks) and ensure smooth transition, as moving applications between projects will eventually require downtime. {% endnote %} -[**Learn how to manage your projects**][project-management-page]. +[Learn how to manage your projects][project-management-page]. ## Why use Projects? @@ -23,7 +23,7 @@ In the near future, Projects will become the cornerstone for application billing ## Default Project -Every owner starts with a Project named default, which serves as the initial workspace. This Project can be renamed at any time to better reflect the organization’s needs. +The project named **defaul**t** is created automatically when your account is set up. By default, this project is used for any application or resource that is not explicitly assigned to another project. You can rename this project at any time, or designate any of your other projects as the new default one to better match your organization’s needs. ## Current Limitations From 270d2493ca8049719f21c9e9e2d47fa32484052a Mon Sep 17 00:00:00 2001 From: Benjamin Date: Fri, 29 Aug 2025 18:24:50 +0200 Subject: [PATCH 18/39] fix link --- src/_posts/platform/projects/2000-01-01-manage-projects.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index ec6b57935..7c84cd298 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -15,7 +15,7 @@ All existing resources have been assigned to a project named **default**. You ca Grouping your applications into projects now will ease the transition to upcoming features and avoid downtime when moving applications later. {% endnote %} -[Learn more about Projects][[projects-overview]. +[Learn more about Projects][projects-overview]. ## Setting the project at App creation From fcecd933af2200a24233c30810f6e45dcc8056d6 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 1 Sep 2025 11:33:55 +0200 Subject: [PATCH 19/39] Fix typo --- src/_posts/platform/projects/2000-01-01-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index a8cf45fb3..c404f9285 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -23,7 +23,7 @@ In the near future, Projects will become the cornerstone for application billing ## Default Project -The project named **defaul**t** is created automatically when your account is set up. By default, this project is used for any application or resource that is not explicitly assigned to another project. You can rename this project at any time, or designate any of your other projects as the new default one to better match your organization’s needs. +The project named **default** is created automatically when your account is set up. By default, this project is used for any application or resource that is not explicitly assigned to another project. You can rename this project at any time, or designate any of your other projects as the new default one to better match your organization’s needs. ## Current Limitations From fd20398103205d54b838820cfb2c00b551332593 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 1 Sep 2025 14:38:37 +0200 Subject: [PATCH 20/39] Align the CLI output with the provided example --- .../projects/2000-01-01-manage-projects.md | 21 +++++++++---------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 7c84cd298..d06d67e0f 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -26,7 +26,7 @@ Within the App creation wizard, the section **Project** enables you to set a pro If the project you'd like to set against the new App, doesn't exist, proceed as follows: 1. Click **+ New project** -2. Enter the project name of your choice (only characters a-Z 0-9 - _ are allowed) +2. Enter the project name of your choice (1–64 characters, using only a–Z, 0–9, -, or _) 3. Click **Add** If the project is in the list @@ -43,19 +43,18 @@ If the project is in the list The output should look like this: ```shell /!\ This command only displays projects where you are the owner - ┌─────────────────────────────┬──────────┬─────────────────────────────────┐ - │ NAME │ DEFAULT │ ID │ - ├─────────────────────────────┼──────────┼─────────────────────────────────┤ - │ project_boo │ false │ prj-0c1ab18c-6ac8-4f85-b55e-b14 │ - │ projectBar │ false │ prj-0c1ab74c-6ac8-7k125-b5e-b7 │ - | default │ true │ prj-0c1adc1c-1ad8-4f85-b55e-z9 │ - └─────────────────────────────┴──────────┴─────────────────────────────────┘ + ┌──────────────┬─────────┬──────────────────────────────────────────┐ + │ NAME │ DEFAULT │ ID │ + ├──────────────┼─────────┼──────────────────────────────────────────┤ + │ test-project │ false │ prj-6731a609-02b6-4614-b28d-5abe43654333 │ + │ default │ true │ prj-20f1b7e4-cf4d-46e9-aff1-e47ae149c444 │ + └──────────────┴─────────┴──────────────────────────────────────────┘ ``` 3. From the command line, set the project at the app creation step: ```shell - scalingo create --project-id=prj-6731a609-02b6-4614-b28d test-app + scalingo create --project-id=prj-6731a609-02b6-4614-b28d-5abe43654333 test-app ``` The output should look like this: ```shell @@ -63,7 +62,7 @@ If the project is in the list To deploy your application, run these commands in your GIT repository: ... ``` -Here you've created the App named `test-app` and set the project, which id is `prj-6731a609-02b6-4614-b28d`, on it +Here you've created the App named `test-app` and set the project, which id is `prj-6731a609-02b6-4614-b28d-5abe43654333`, on it ### Using the Terraform Provider @@ -90,7 +89,7 @@ Here you've created the App named `test-app` and set the project, which id is `p If the project isn't already existing, proceed as follows: 1. Click **+ New project** -2. Enter the project name of your choice (only characters a-Z 0-9 - _ are allowed) +2. Enter the project name of your choice (1-64 characters, using only a–Z, 0–9, -, or _) 3. Click **Add** From cc935b5fbca4e74e00751a97716c4f0cb5844adc Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 1 Sep 2025 15:08:45 +0200 Subject: [PATCH 21/39] Update project constraints: no capital letters allowed, default limit to 20 projects. --- src/_posts/platform/projects/2000-01-01-manage-projects.md | 4 ++-- src/_posts/platform/projects/2000-01-01-overview.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index d06d67e0f..7217f9efa 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -26,7 +26,7 @@ Within the App creation wizard, the section **Project** enables you to set a pro If the project you'd like to set against the new App, doesn't exist, proceed as follows: 1. Click **+ New project** -2. Enter the project name of your choice (1–64 characters, using only a–Z, 0–9, -, or _) +2. Enter the project name of your choice (1–64 characters, using only a-z, 0-9, -, or _) 3. Click **Add** If the project is in the list @@ -89,7 +89,7 @@ Here you've created the App named `test-app` and set the project, which id is `p If the project isn't already existing, proceed as follows: 1. Click **+ New project** -2. Enter the project name of your choice (1-64 characters, using only a–Z, 0–9, -, or _) +2. Enter the project name of your choice (1-64 characters, using only a-z, 0-9, -, or _) 3. Click **Add** diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index c404f9285..e22ac6818 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -30,7 +30,7 @@ The project named **default** is created automatically when your account is set - Currently, only the owner of a project or an app can move an application between projects. - Projects cannot be deleted from the Dashboard, they can only be [removed using the CLI or API][removing-project]. - Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. -- Accounts are limited to 100 projects to prevent abuse. This limit can be raised depending on your needs by contacting our support team. +- Accounts are limited to 20 projects to prevent abuse. This limit can be raised depending on your needs by contacting our support team. [project-management-page]: {% post_url platform/projects/2000-01-01-manage-projects %} [removing-project]: {% post_url platform/projects/2000-01-01-manage-projects %}#removing-a-project From 7bea2bc264ea005dbaddd96075a4b17d983a524b Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 1 Sep 2025 17:33:30 +0200 Subject: [PATCH 22/39] =?UTF-8?q?Update=20our=20message=20about=20the=20tr?= =?UTF-8?q?ansition=20phase=20between=20=E2=80=9Cflexible=E2=80=9D=20and?= =?UTF-8?q?=20=E2=80=9Cisolated=E2=80=9D=20projects.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../projects/2000-01-01-manage-projects.md | 10 ++++---- .../platform/projects/2000-01-01-overview.md | 24 +++++++++++++++---- 2 files changed, 25 insertions(+), 9 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 7217f9efa..3cd6e7659 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -7,13 +7,13 @@ index: 2 ## Introduction -Projects offer a new way to organize your applications. +Projects are the way to organize your applications and resources on Scalingo. -All existing resources have been assigned to a project named **default**. You can rename this project or move resources to another project at any time. +All existing resources have automatically been assigned to a project named **default**. You can rename this project, move resources into another project, or set a different project as the new default at any time. -{% note %} -Grouping your applications into projects now will ease the transition to upcoming features and avoid downtime when moving applications later. -{% endnote %} +{% warning %} +We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. +{% endwarning %} [Learn more about Projects][projects-overview]. diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index e22ac6818..5a9839ce3 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -5,13 +5,16 @@ tags: project overview index: 1 --- -Projects offer a new way to organize your applications. By grouping your resources into projects now, you are preparing for upcoming features focused on the network isolation of your applications and environments. +Projects offer a new way to organize your applications and resources. They let you group applications into logical units that reflect your organization's structure: by product, customer, environment, or any other approach that fits your needs. {% note %} -We encourage you to group your applications into projects now. -This will prepare you for upcoming features (such as private networks) and ensure smooth transition, as moving applications between projects will eventually require downtime. +Today, projects are flexible: applications can still be regrouped freely. But starting **March 1, 2026**, projects will become isolated, each running on its own dedicated network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. {% endnote %} +{% warning %} +We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. +{% endwarning %} + [Learn how to manage your projects][project-management-page]. ## Why use Projects? @@ -23,7 +26,7 @@ In the near future, Projects will become the cornerstone for application billing ## Default Project -The project named **default** is created automatically when your account is set up. By default, this project is used for any application or resource that is not explicitly assigned to another project. You can rename this project at any time, or designate any of your other projects as the new default one to better match your organization’s needs. +The project named **default** is created automatically when your account is set up. By default, this project is used for any application or resource that is not explicitly assigned to another project. You can rename this project at any time, or designate any of your other projects as the new default one to better match your organization's needs. ## Current Limitations @@ -32,5 +35,18 @@ The project named **default** is created automatically when your account is set - Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. - Accounts are limited to 20 projects to prevent abuse. This limit can be raised depending on your needs by contacting our support team. +## Transition Period: From Flexible to Isolated Projects + +To prepare for the activation of advanced networking features, we are introducing a transition period with clear milestones: + +- September 15, 2025: start of the transition period with the introduction of Projects in beta. At this stage, projects are still flexible, meaning applications can be regrouped freely between them. +- Q1 2026: new interfaces will be introduced to simplify the management of isolated projects and ease the transition. +- By March 1, 2026: **projects will become isolated**, each running on its own Private Network. From this date, applications can no longer be regrouped between projects. +- After this date, moving a single application will no longer be possible. Instead, entire projects will need to be transferred as a unit. + +{% warning %} +We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition from today's flexible model to tomorrow's isolated and secure environments. +{% endwarning %} + [project-management-page]: {% post_url platform/projects/2000-01-01-manage-projects %} [removing-project]: {% post_url platform/projects/2000-01-01-manage-projects %}#removing-a-project From 8c76d72fa493e1a98d5dd11df833e2ff08a36ce1 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 1 Sep 2025 17:51:30 +0200 Subject: [PATCH 23/39] Fix typo --- src/_posts/platform/projects/2000-01-01-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index 5a9839ce3..f82c3ed2d 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -8,7 +8,7 @@ index: 1 Projects offer a new way to organize your applications and resources. They let you group applications into logical units that reflect your organization's structure: by product, customer, environment, or any other approach that fits your needs. {% note %} -Today, projects are flexible: applications can still be regrouped freely. But starting **March 1, 2026**, projects will become isolated, each running on its own dedicated network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. +Today, projects are flexible: applications can still be regrouped freely. But starting **March 1, 2026**, projects will become isolated, each running on its own private network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. {% endnote %} {% warning %} From 4a36edc363671aa3801f874677f0a6a276b9a13c Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 1 Sep 2025 18:00:44 +0200 Subject: [PATCH 24/39] Update the transition phase wording to introduce private networks --- .../projects/2000-01-01-manage-projects.md | 2 +- .../platform/projects/2000-01-01-overview.md | 16 ++++++++-------- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 3cd6e7659..3fb622865 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -12,7 +12,7 @@ Projects are the way to organize your applications and resources on Scalingo. All existing resources have automatically been assigned to a project named **default**. You can rename this project, move resources into another project, or set a different project as the new default at any time. {% warning %} -We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. +We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. {% endwarning %} [Learn more about Projects][projects-overview]. diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index f82c3ed2d..d14bb42a1 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -5,14 +5,14 @@ tags: project overview index: 1 --- -Projects offer a new way to organize your applications and resources. They let you group applications into logical units that reflect your organization's structure: by product, customer, environment, or any other approach that fits your needs. +Projects offer a new way to organize your applications and resources. They let you group applications into logical units that reflect your organization's structure: by product, customer, environment, or any other approach that fits your needs. {% note %} Today, projects are flexible: applications can still be regrouped freely. But starting **March 1, 2026**, projects will become isolated, each running on its own private network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. {% endnote %} {% warning %} -We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. +We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. {% endwarning %} [Learn how to manage your projects][project-management-page]. @@ -35,17 +35,17 @@ The project named **default** is created automatically when your account is set - Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. - Accounts are limited to 20 projects to prevent abuse. This limit can be raised depending on your needs by contacting our support team. -## Transition Period: From Flexible to Isolated Projects +## Transition towards Private Networks -To prepare for the activation of advanced networking features, we are introducing a transition period with clear milestones: +To prepare for the activation of private networks, we are introducing a transition period with clear milestones: -- September 15, 2025: start of the transition period with the introduction of Projects in beta. At this stage, projects are still flexible, meaning applications can be regrouped freely between them. -- Q1 2026: new interfaces will be introduced to simplify the management of isolated projects and ease the transition. -- By March 1, 2026: **projects will become isolated**, each running on its own Private Network. From this date, applications can no longer be regrouped between projects. +- September 15, 2025: start of the transition period with the introduction of Projects. At this stage, projects remain flexible, and applications can still be regrouped freely. +- Q1 2026: new interfaces will be introduced to simplify project management and make working with private networks more seamless. +- By March 1, 2026: each project will run on its own private network. From this date, applications can no longer be regrouped between projects. - After this date, moving a single application will no longer be possible. Instead, entire projects will need to be transferred as a unit. {% warning %} -We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition from today's flexible model to tomorrow's isolated and secure environments. +We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition to private networks. {% endwarning %} [project-management-page]: {% post_url platform/projects/2000-01-01-manage-projects %} From c63d15e7122b27ed416e1f358f8799eab4443de4 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Wed, 3 Sep 2025 09:43:14 +0200 Subject: [PATCH 25/39] Update src/_posts/platform/projects/2000-01-01-manage-projects.md Co-authored-by: matthieu526-scalingo --- src/_posts/platform/projects/2000-01-01-manage-projects.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 3fb622865..1429a3ff1 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -62,7 +62,7 @@ If the project is in the list To deploy your application, run these commands in your GIT repository: ... ``` -Here you've created the App named `test-app` and set the project, which id is `prj-6731a609-02b6-4614-b28d-5abe43654333`, on it +Here you've created the app named `test-app` and set the project ID to `prj-6731a609-02b6-4614-b28d-5abe43654333`. ### Using the Terraform Provider From 4ebad6ee7ae0c900ab1efe52af55e353dca8a4a5 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Wed, 3 Sep 2025 09:50:21 +0200 Subject: [PATCH 26/39] Include suggestions from the review --- src/_posts/platform/projects/2000-01-01-overview.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index d14bb42a1..5c299db8f 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -8,11 +8,11 @@ index: 1 Projects offer a new way to organize your applications and resources. They let you group applications into logical units that reflect your organization's structure: by product, customer, environment, or any other approach that fits your needs. {% note %} -Today, projects are flexible: applications can still be regrouped freely. But starting **March 1, 2026**, projects will become isolated, each running on its own private network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. +Today, projects are flexible: applications can still be moved or regrouped freely. But starting **March 1, 2026**, projects will become isolated, each running on its own private network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. {% endnote %} {% warning %} -We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. +We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped or moved between projects, except by recreating them in the target project. {% endwarning %} [Learn how to manage your projects][project-management-page]. @@ -31,7 +31,7 @@ The project named **default** is created automatically when your account is set ## Current Limitations - Currently, only the owner of a project or an app can move an application between projects. -- Projects cannot be deleted from the Dashboard, they can only be [removed using the CLI or API][removing-project]. +- Projects cannot be deleted from the Dashboard, they can be [removed using the CLI, API or Terraform][removing-project]. - Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. - Accounts are limited to 20 projects to prevent abuse. This limit can be raised depending on your needs by contacting our support team. From ea19082980cb7b3e2d0d7adfa1b7d5b354ed33e9 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Wed, 3 Sep 2025 14:47:19 +0200 Subject: [PATCH 27/39] =?UTF-8?q?Include=20Fran=C3=A7ois's=20suggestions?= =?UTF-8?q?=20to=20declutter=20the=20manage=20page=20and=20move=20temporar?= =?UTF-8?q?y=20information=20into=20the=20transition=20timeline.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../platform/projects/2000-01-01-manage-projects.md | 8 ++------ src/_posts/platform/projects/2000-01-01-overview.md | 3 ++- 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 1429a3ff1..f7ef95ef5 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -1,22 +1,18 @@ --- title: Manage your Projects -modified_at: 2025-08-29 07:00:00 +modified_at: 2025-09-03 07:00:00 tags: project management index: 2 --- -## Introduction - Projects are the way to organize your applications and resources on Scalingo. -All existing resources have automatically been assigned to a project named **default**. You can rename this project, move resources into another project, or set a different project as the new default at any time. +[Learn more about Projects][projects-overview]. {% warning %} We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. {% endwarning %} -[Learn more about Projects][projects-overview]. - ## Setting the project at App creation ### Using the Dashboard diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index 5c299db8f..d56aa91c0 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -1,6 +1,6 @@ --- title: Projects Overview -modified_at: 2025-08-29 07:00:00 +modified_at: 2025-09-03 07:00:00 tags: project overview index: 1 --- @@ -39,6 +39,7 @@ The project named **default** is created automatically when your account is set To prepare for the activation of private networks, we are introducing a transition period with clear milestones: +- September 1, 2025: all existing resources have automatically been assigned to a Project named **default**. - September 15, 2025: start of the transition period with the introduction of Projects. At this stage, projects remain flexible, and applications can still be regrouped freely. - Q1 2026: new interfaces will be introduced to simplify project management and make working with private networks more seamless. - By March 1, 2026: each project will run on its own private network. From this date, applications can no longer be regrouped between projects. From 83d32c562066f6f5be50aa1ed897d8c626f85970 Mon Sep 17 00:00:00 2001 From: Stephane Le Choisnier Date: Thu, 4 Sep 2025 15:06:24 +0200 Subject: [PATCH 28/39] Minor changes proposed (indentation, font style and cases) --- src/_posts/platform/projects/2000-01-01-overview.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index d56aa91c0..51fdf41f8 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -8,7 +8,9 @@ index: 1 Projects offer a new way to organize your applications and resources. They let you group applications into logical units that reflect your organization's structure: by product, customer, environment, or any other approach that fits your needs. {% note %} -Today, projects are flexible: applications can still be moved or regrouped freely. But starting **March 1, 2026**, projects will become isolated, each running on its own private network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. +**Today** projects are flexible: applications can still be moved or regrouped freely. + +Starting **March 1, 2026**, projects will become isolated, each running on its own private network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. {% endnote %} {% warning %} @@ -22,7 +24,7 @@ We strongly recommend grouping your applications into projects before **March 1, Projects provide a structured way to separate applications according to your own logic, whether by product, customer, environment, or any other approach that fits your needs. This makes large accounts easier to navigate and manage, while keeping resources clearly organized. -In the near future, Projects will become the cornerstone for application billing, security, and network isolation. While these advanced features are not yet available, introducing Projects today gives you the opportunity to start aligning your applications with this organizational model. By grouping your apps into Projects now, you will be better prepared to take full advantage of these upcoming capabilities. +In a near future, Projects will become the cornerstone for application billing, security, and network isolation. While these advanced features are not yet available, introducing Projects today gives you the opportunity to start aligning your applications with this organizational model. By grouping your apps into Projects now, you will be better prepared to take full advantage of these upcoming capabilities. ## Default Project @@ -33,11 +35,11 @@ The project named **default** is created automatically when your account is set - Currently, only the owner of a project or an app can move an application between projects. - Projects cannot be deleted from the Dashboard, they can be [removed using the CLI, API or Terraform][removing-project]. - Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. -- Accounts are limited to 20 projects to prevent abuse. This limit can be raised depending on your needs by contacting our support team. +- Accounts are limited to 20 projects to prevent misuse. This limit can be raised depending on your needs by contacting our support team. ## Transition towards Private Networks -To prepare for the activation of private networks, we are introducing a transition period with clear milestones: +To prepare for the activation of Private Networks, we are introducing a transition period with clear milestones: - September 1, 2025: all existing resources have automatically been assigned to a Project named **default**. - September 15, 2025: start of the transition period with the introduction of Projects. At this stage, projects remain flexible, and applications can still be regrouped freely. @@ -46,7 +48,7 @@ To prepare for the activation of private networks, we are introducing a transiti - After this date, moving a single application will no longer be possible. Instead, entire projects will need to be transferred as a unit. {% warning %} -We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition to private networks. +We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition to Private Networks. {% endwarning %} [project-management-page]: {% post_url platform/projects/2000-01-01-manage-projects %} From 51d168e35d79a491c7e1babd9080e04bc5a8468f Mon Sep 17 00:00:00 2001 From: Benjamin Date: Fri, 5 Sep 2025 16:11:50 +0200 Subject: [PATCH 29/39] Improve transitions phases wording. --- src/_posts/platform/projects/2000-01-01-overview.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index 51fdf41f8..c10cdde35 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -43,9 +43,10 @@ To prepare for the activation of Private Networks, we are introducing a transiti - September 1, 2025: all existing resources have automatically been assigned to a Project named **default**. - September 15, 2025: start of the transition period with the introduction of Projects. At this stage, projects remain flexible, and applications can still be regrouped freely. -- Q1 2026: new interfaces will be introduced to simplify project management and make working with private networks more seamless. +- New interfaces will be introduced ahead of the network isolation deadline to simplify project management and improve the experience with private networks. - By March 1, 2026: each project will run on its own private network. From this date, applications can no longer be regrouped between projects. -- After this date, moving a single application will no longer be possible. Instead, entire projects will need to be transferred as a unit. +- After this date, moving a single application from one project to another will no longer be possible. Changing a project for an application will require recreating and redeploying it in the target project. +- Additionally, we will introduce the ability to transfer entire projects to another owner, making collaboration and handovers easier. {% warning %} We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition to Private Networks. From 584467de9d21a1cd4577d353e2f85857b4fcb3e1 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 8 Sep 2025 10:54:10 +0200 Subject: [PATCH 30/39] Minor wording change to highlight more clearly the benefits and limitations of private networks. --- src/_posts/platform/projects/2000-01-01-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index c10cdde35..adbe50e5c 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -24,7 +24,7 @@ We strongly recommend grouping your applications into projects before **March 1, Projects provide a structured way to separate applications according to your own logic, whether by product, customer, environment, or any other approach that fits your needs. This makes large accounts easier to navigate and manage, while keeping resources clearly organized. -In a near future, Projects will become the cornerstone for application billing, security, and network isolation. While these advanced features are not yet available, introducing Projects today gives you the opportunity to start aligning your applications with this organizational model. By grouping your apps into Projects now, you will be better prepared to take full advantage of these upcoming capabilities. +In the near future, Projects will also become the cornerstone of application billing, security, and, most importantly, network isolation. Each project will operate on its own private network, isolated from the others. By starting to group your applications into Projects today, you ensure that your organization is ready for this model and will be able to take full advantage of the upcoming private networking capabilities. ## Default Project From 11b9c40a7a2ef598590c6ac8f0b6df8f624d3c40 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 8 Sep 2025 11:10:05 +0200 Subject: [PATCH 31/39] Add a changelog entry --- src/changelog/features/_posts/2025-09-10-projects.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 src/changelog/features/_posts/2025-09-10-projects.md diff --git a/src/changelog/features/_posts/2025-09-10-projects.md b/src/changelog/features/_posts/2025-09-10-projects.md new file mode 100644 index 000000000..343e00944 --- /dev/null +++ b/src/changelog/features/_posts/2025-09-10-projects.md @@ -0,0 +1,12 @@ +--- +modified_at: 2025-09-08 06:00:00 +title: 'Introducing Projects' +--- + +We are introducing **[Projects]({% post_url platform/projects/2000-01-01-overview %})** to help you organize and structure your applications more effectively. + +Projects provide a flexible way to group your applications according to your own logic: by product, customer, environment, or any other approach that fits your needs. This makes large accounts easier to navigate and manage, while keeping resources clearly separated. + +By starting to use Projects now, you will also be preparing for upcoming **Private Networks**, which will allow applications within the same project to communicate securely in an isolated environment. + +👉 [Learn how to get started with Projects]({% post_url platform/projects/2000-01-01-overview %}) From b0223db60582be1252eb9b0e94c79379527f6594 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 8 Sep 2025 14:31:22 +0200 Subject: [PATCH 32/39] Fix dates --- .../features/_posts/2025-07-17-limited-collaborator-role.md | 2 +- .../_posts/{2025-09-10-projects.md => 2025-09-08-projects.md} | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename src/changelog/features/_posts/{2025-09-10-projects.md => 2025-09-08-projects.md} (100%) diff --git a/src/changelog/features/_posts/2025-07-17-limited-collaborator-role.md b/src/changelog/features/_posts/2025-07-17-limited-collaborator-role.md index 0e7d2b20f..99db23faf 100644 --- a/src/changelog/features/_posts/2025-07-17-limited-collaborator-role.md +++ b/src/changelog/features/_posts/2025-07-17-limited-collaborator-role.md @@ -1,5 +1,5 @@ --- -modified_at: 2025-07-17 06:00:00 +modified_at: 2025-09-17 06:00:00 title: 'Introducing the Limited Collaborator Role' --- diff --git a/src/changelog/features/_posts/2025-09-10-projects.md b/src/changelog/features/_posts/2025-09-08-projects.md similarity index 100% rename from src/changelog/features/_posts/2025-09-10-projects.md rename to src/changelog/features/_posts/2025-09-08-projects.md From 44da86969c860a0090cdcf0147533d0c82ab3811 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 8 Sep 2025 14:45:12 +0200 Subject: [PATCH 33/39] Revert date of the limited collaborator changelog note. --- .../features/_posts/2025-07-17-limited-collaborator-role.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/changelog/features/_posts/2025-07-17-limited-collaborator-role.md b/src/changelog/features/_posts/2025-07-17-limited-collaborator-role.md index 99db23faf..0e7d2b20f 100644 --- a/src/changelog/features/_posts/2025-07-17-limited-collaborator-role.md +++ b/src/changelog/features/_posts/2025-07-17-limited-collaborator-role.md @@ -1,5 +1,5 @@ --- -modified_at: 2025-09-17 06:00:00 +modified_at: 2025-07-17 06:00:00 title: 'Introducing the Limited Collaborator Role' --- From dfdfaec162f7b39cd11eade24c4b28708428c5d4 Mon Sep 17 00:00:00 2001 From: Stephane Le Choisnier Date: Mon, 8 Sep 2025 14:37:09 +0200 Subject: [PATCH 34/39] Added details about the update of project name and defaut attribute, plus the change from "app management" to "General" --- .../platform/projects/2000-01-01-manage-projects.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index f7ef95ef5..1ef833181 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -78,7 +78,7 @@ Here you've created the app named `test-app` and set the project ID to `prj-6731 2. Click the **Apps** tab 3. Click on the application for which you want to manage the project 4. Click the **Settings** tab -5. In the **Settings** submenu, make sure to select **App management** +5. In the **Settings** submenu, make sure to select **General** 6. In the section **Parent project**, click **Move app to another project** @@ -172,7 +172,13 @@ Two attributes can be updated: `name` and `default`. ### Using the Dashboard -This feature is not yet available in the dashboard. +1. From your web browser, open your [dashboard][dashboard] +2. Click the **Apps** tab +3. Click on the application for which you want to edit the project +4. Click the **Settings** tab, make sure to select **General** +5. Click **`your-project` settings** (where `your-project` is the current name of the project you want to edit) +6. Edit either the `name` of the project or tick the checkbox to make it the `default` project or update both +7. Click **Edit** ### Using the Command Line From cab78b1f37f0d2e126f3493a6fb2ccf4a8005340 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Mon, 8 Sep 2025 17:16:04 +0200 Subject: [PATCH 35/39] Rename another mention from "App management" to "General". --- src/_posts/platform/app/2000-01-01-review-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/platform/app/2000-01-01-review-apps.md b/src/_posts/platform/app/2000-01-01-review-apps.md index 7d656ce00..050b4edcf 100644 --- a/src/_posts/platform/app/2000-01-01-review-apps.md +++ b/src/_posts/platform/app/2000-01-01-review-apps.md @@ -29,7 +29,7 @@ delay to fit your needs. This latter setting means that you can still review PR after your dev team has closed the PR. The owner of the parent application is the only account which can manually delete the review app, via -the Settings menu of *the review app*, submenu App management, in the dashboard, or via our [CLI](https://developers.scalingo.com/apps#delete-an-application). +the Settings menu of *the review app*, submenu **General**, in the dashboard, or via our [CLI](https://developers.scalingo.com/apps#delete-an-application). {% warning %} The procedure to delete a standard application is similar. Ensure you're deleting the review app before proceeding. From bd6747476ac155952b89c544d295942f7dd561eb Mon Sep 17 00:00:00 2001 From: Benjamin Date: Tue, 9 Sep 2025 11:29:29 +0200 Subject: [PATCH 36/39] Update dates --- src/_posts/platform/projects/2000-01-01-manage-projects.md | 2 +- src/_posts/platform/projects/2000-01-01-overview.md | 2 +- src/changelog/features/_posts/2025-09-08-projects.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 1ef833181..895efb5ff 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -1,6 +1,6 @@ --- title: Manage your Projects -modified_at: 2025-09-03 07:00:00 +modified_at: 2025-09-09 07:00:00 tags: project management index: 2 --- diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index adbe50e5c..ed44cfa2c 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -1,6 +1,6 @@ --- title: Projects Overview -modified_at: 2025-09-03 07:00:00 +modified_at: 2025-09-09 07:00:00 tags: project overview index: 1 --- diff --git a/src/changelog/features/_posts/2025-09-08-projects.md b/src/changelog/features/_posts/2025-09-08-projects.md index 343e00944..db2170876 100644 --- a/src/changelog/features/_posts/2025-09-08-projects.md +++ b/src/changelog/features/_posts/2025-09-08-projects.md @@ -1,5 +1,5 @@ --- -modified_at: 2025-09-08 06:00:00 +modified_at: 2025-09-11 07:00:00 title: 'Introducing Projects' --- From b90b46c797527959046db05de30b9412d1ed8c37 Mon Sep 17 00:00:00 2001 From: Benjamin Date: Tue, 9 Sep 2025 16:07:56 +0200 Subject: [PATCH 37/39] Update overview and changelog to reflect Projects as core platform element, decoupled from Private Networks. --- .../projects/2000-01-01-manage-projects.md | 2 +- .../platform/projects/2000-01-01-overview.md | 15 +++++++-------- .../features/_posts/2025-09-08-projects.md | 2 +- 3 files changed, 9 insertions(+), 10 deletions(-) diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md index 895efb5ff..9e6c54f34 100644 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ b/src/_posts/platform/projects/2000-01-01-manage-projects.md @@ -234,4 +234,4 @@ remove the associated resource from the Terraform file. [dashboard]: https://dashboard.scalingo.com/ [cli]: {% post_url platform/cli/2000-01-01-start %} -[projects-overview]: {% post_url platform/projects/2000-01-01-overview %} \ No newline at end of file +[projects-overview]: {% post_url platform/projects/2000-01-01-overview %} diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md index ed44cfa2c..aa725376b 100644 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ b/src/_posts/platform/projects/2000-01-01-overview.md @@ -10,7 +10,7 @@ Projects offer a new way to organize your applications and resources. They let y {% note %} **Today** projects are flexible: applications can still be moved or regrouped freely. -Starting **March 1, 2026**, projects will become isolated, each running on its own private network. This shift will strengthen security and isolation, while requiring you to structure your applications in projects ahead of time. +Starting **March 1, 2026**, projects will become a core structural element of the Scalingo platform. This means that applications will no longer be movable between projects, and projects themselves will serve as the foundation for future platform features. {% endnote %} {% warning %} @@ -24,7 +24,7 @@ We strongly recommend grouping your applications into projects before **March 1, Projects provide a structured way to separate applications according to your own logic, whether by product, customer, environment, or any other approach that fits your needs. This makes large accounts easier to navigate and manage, while keeping resources clearly organized. -In the near future, Projects will also become the cornerstone of application billing, security, and, most importantly, network isolation. Each project will operate on its own private network, isolated from the others. By starting to group your applications into Projects today, you ensure that your organization is ready for this model and will be able to take full advantage of the upcoming private networking capabilities. +In the near future, Projects will also become the cornerstone of application billing, advanced access controls, and network-related security features. Private networks are one of the upcoming capabilities that will build on top of Projects. By starting to group your applications into Projects today, you ensure that your organization is ready to take full advantage of these future improvements. ## Default Project @@ -37,19 +37,18 @@ The project named **default** is created automatically when your account is set - Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. - Accounts are limited to 20 projects to prevent misuse. This limit can be raised depending on your needs by contacting our support team. -## Transition towards Private Networks +## Transition Timeline -To prepare for the activation of Private Networks, we are introducing a transition period with clear milestones: +We are introducing a transition period with clear milestones: - September 1, 2025: all existing resources have automatically been assigned to a Project named **default**. - September 15, 2025: start of the transition period with the introduction of Projects. At this stage, projects remain flexible, and applications can still be regrouped freely. -- New interfaces will be introduced ahead of the network isolation deadline to simplify project management and improve the experience with private networks. -- By March 1, 2026: each project will run on its own private network. From this date, applications can no longer be regrouped between projects. +- Ahead of March 1, 2026: new interfaces and management capabilities will be introduced to strengthen the role of Projects as a core element of the platform and improve the overall experience. +- By March 1, 2026: Projects will become a fixed and foundational component of the platform. From this date, applications can no longer be regrouped between projects. - After this date, moving a single application from one project to another will no longer be possible. Changing a project for an application will require recreating and redeploying it in the target project. -- Additionally, we will introduce the ability to transfer entire projects to another owner, making collaboration and handovers easier. {% warning %} -We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition to Private Networks. +We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition as they become a core element of the Scalingo platform. {% endwarning %} [project-management-page]: {% post_url platform/projects/2000-01-01-manage-projects %} diff --git a/src/changelog/features/_posts/2025-09-08-projects.md b/src/changelog/features/_posts/2025-09-08-projects.md index db2170876..86254b936 100644 --- a/src/changelog/features/_posts/2025-09-08-projects.md +++ b/src/changelog/features/_posts/2025-09-08-projects.md @@ -7,6 +7,6 @@ We are introducing **[Projects]({% post_url platform/projects/2000-01-01-overvie Projects provide a flexible way to group your applications according to your own logic: by product, customer, environment, or any other approach that fits your needs. This makes large accounts easier to navigate and manage, while keeping resources clearly separated. -By starting to use Projects now, you will also be preparing for upcoming **Private Networks**, which will allow applications within the same project to communicate securely in an isolated environment. +Over time, Projects will evolve into a **core building block of the Scalingo platform**, serving as the foundation for new features in billing, access management, and network security. One of the upcoming capabilities will be **Private Networks**, enabling applications within the same project to communicate securely in an isolated environment. 👉 [Learn how to get started with Projects]({% post_url platform/projects/2000-01-01-overview %}) From f853802bff4d7baf95acc89d57db421f302d9b61 Mon Sep 17 00:00:00 2001 From: Annabelle PELLIER Date: Wed, 10 Sep 2025 09:37:01 +0200 Subject: [PATCH 38/39] replace mono font --- assets/style.css | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/style.css b/assets/style.css index e9abe79b5..701bae75b 100644 --- a/assets/style.css +++ b/assets/style.css @@ -32,7 +32,7 @@ /* fonts */ --font-sans: "aktiv-grotesk"; --font-serif: "freight-text-pro"; - --font-mono: "fira-mono"; + --font-mono: "Menlo"; /* width */ --sc-container: "1440px"; From ed6157057dea03f92621e5ff1bd45f8ebde36c78 Mon Sep 17 00:00:00 2001 From: Annabelle PELLIER Date: Wed, 10 Sep 2025 09:49:33 +0200 Subject: [PATCH 39/39] remove projects changes --- src/_posts/platform/2000-01-01-projects.md | 4 - .../app/2000-01-01-lifecycle-management.md | 3 - .../platform/app/2000-01-01-review-apps.md | 2 +- .../projects/2000-01-01-manage-projects.md | 237 ------------------ .../platform/projects/2000-01-01-overview.md | 55 ---- .../features/_posts/2025-09-08-projects.md | 12 - 6 files changed, 1 insertion(+), 312 deletions(-) delete mode 100644 src/_posts/platform/2000-01-01-projects.md delete mode 100644 src/_posts/platform/projects/2000-01-01-manage-projects.md delete mode 100644 src/_posts/platform/projects/2000-01-01-overview.md delete mode 100644 src/changelog/features/_posts/2025-09-08-projects.md diff --git a/src/_posts/platform/2000-01-01-projects.md b/src/_posts/platform/2000-01-01-projects.md deleted file mode 100644 index ebae6994a..000000000 --- a/src/_posts/platform/2000-01-01-projects.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -title: Projects -index: 5 ---- \ No newline at end of file diff --git a/src/_posts/platform/app/2000-01-01-lifecycle-management.md b/src/_posts/platform/app/2000-01-01-lifecycle-management.md index c2029a675..14cf677cd 100644 --- a/src/_posts/platform/app/2000-01-01-lifecycle-management.md +++ b/src/_posts/platform/app/2000-01-01-lifecycle-management.md @@ -45,9 +45,6 @@ $ scalingo create my-app --remote staging # Create a new app with a custom buildpack $ scalingo create my-app --buildpack https://github.com/Scalingo/multi-buildpack - -# Create a new app in the chosen project -$ scalingo create --project-id=prj-6731a609-02b6-4614-b28d-5abe43654333 my-app ``` ## Rename an Application diff --git a/src/_posts/platform/app/2000-01-01-review-apps.md b/src/_posts/platform/app/2000-01-01-review-apps.md index 050b4edcf..7d656ce00 100644 --- a/src/_posts/platform/app/2000-01-01-review-apps.md +++ b/src/_posts/platform/app/2000-01-01-review-apps.md @@ -29,7 +29,7 @@ delay to fit your needs. This latter setting means that you can still review PR after your dev team has closed the PR. The owner of the parent application is the only account which can manually delete the review app, via -the Settings menu of *the review app*, submenu **General**, in the dashboard, or via our [CLI](https://developers.scalingo.com/apps#delete-an-application). +the Settings menu of *the review app*, submenu App management, in the dashboard, or via our [CLI](https://developers.scalingo.com/apps#delete-an-application). {% warning %} The procedure to delete a standard application is similar. Ensure you're deleting the review app before proceeding. diff --git a/src/_posts/platform/projects/2000-01-01-manage-projects.md b/src/_posts/platform/projects/2000-01-01-manage-projects.md deleted file mode 100644 index 9e6c54f34..000000000 --- a/src/_posts/platform/projects/2000-01-01-manage-projects.md +++ /dev/null @@ -1,237 +0,0 @@ ---- -title: Manage your Projects -modified_at: 2025-09-09 07:00:00 -tags: project management -index: 2 ---- - -Projects are the way to organize your applications and resources on Scalingo. - -[Learn more about Projects][projects-overview]. - -{% warning %} -We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped between projects except by recreating them in the target project. -{% endwarning %} - -## Setting the project at App creation - -### Using the Dashboard - -Within the App creation wizard, the section **Project** enables you to set a project different from **default**. - -If the project you'd like to set against the new App, doesn't exist, proceed as follows: - -1. Click **+ New project** -2. Enter the project name of your choice (1–64 characters, using only a-z, 0-9, -, or _) -3. Click **Add** - -If the project is in the list -1. Select the project you want -2. Proceed with the next steps of your app creation - -### Using the Command Line - -1. Make sure you have correctly [setup the Scalingo command line tool][cli] -2. From the command line, list the projects: - ```shell - scalingo projects - ``` - The output should look like this: - ```shell - /!\ This command only displays projects where you are the owner - ┌──────────────┬─────────┬──────────────────────────────────────────┐ - │ NAME │ DEFAULT │ ID │ - ├──────────────┼─────────┼──────────────────────────────────────────┤ - │ test-project │ false │ prj-6731a609-02b6-4614-b28d-5abe43654333 │ - │ default │ true │ prj-20f1b7e4-cf4d-46e9-aff1-e47ae149c444 │ - └──────────────┴─────────┴──────────────────────────────────────────┘ - ``` - -3. From the command line, set the project at the app creation step: - - ```shell - scalingo create --project-id=prj-6731a609-02b6-4614-b28d-5abe43654333 test-app - ``` - The output should look like this: - ```shell - App 'test-app' has been created - To deploy your application, run these commands in your GIT repository: - ... - ``` -Here you've created the app named `test-app` and set the project ID to `prj-6731a609-02b6-4614-b28d-5abe43654333`. - -### Using the Terraform Provider - -1. Place the following `project_id` in the app `resource` block in your Terraform file: - ```tf - resource "scalingo_app" "test_app" { - name = "terraform-testapp" - project_id = "prj-6731a609-02b6-4614-b28d-5abe43654333" - } - ``` - -## Updating the project of an existing App - -### Using the Dashboard - -1. From your web browser, open your [dashboard][dashboard] -2. Click the **Apps** tab -3. Click on the application for which you want to manage the project -4. Click the **Settings** tab -5. In the **Settings** submenu, make sure to select **General** -6. In the section **Parent project**, click **Move app to another project** - - -If the project isn't already existing, proceed as follows: - -1. Click **+ New project** -2. Enter the project name of your choice (1-64 characters, using only a-z, 0-9, -, or _) -3. Click **Add** - - -If the project is in the list - -1. Select the project you want -2. Click **Move app to project** - -### Using the Command Line - -This feature is not yet available in the CLI. - -### Using the Terraform Provider - -This feature is not yet available in the Terraform Provider. - -## Listing the projects - -{% warning %} -For the moment, listing projects will only return those where you are the owner. -{% endwarning %} - -### Using the Dashboard - -Right now it is only possible to list the projects when creating a new application. - -### Using the Command Line - -1. Make sure you have correctly [setup the Scalingo command line tool][cli] -2. From the command line, list the projects: - ```shell - scalingo projects - ``` - The output should look like this: - ```shell - /!\ This command only displays projects where you are the owner - ┌──────────────┬─────────┬──────────────────────────────────────────┐ - │ NAME │ DEFAULT │ ID │ - ├──────────────┼─────────┼──────────────────────────────────────────┤ - │ test-project │ false │ prj-6731a609-02b6-4614-b28d-5abe43654333 │ - │ default │ true │ prj-20f1b7e4-cf4d-46e9-aff1-e47ae149c444 │ - └──────────────┴─────────┴──────────────────────────────────────────┘ - ``` - -## Creating a new project - -### Using the Dashboard - -Right now it is only possible to create a new project when creating a new application or when moving an existing application to another project. - -### Using the Command Line - -1. Make sure you have correctly [setup the Scalingo command line tool][cli] -2. From the command line, create a project: - ```shell - scalingo projects-add test-project - ``` - The output should look like this: - ```shell - -----> test-project has been created - ``` - You can also create a new project that will be default directly: - ```shell - scalingo projects-add --default test-project - ``` - -### Using the Terraform Provider - -1. Place the following `resource` block in your Terraform file: - ```tf - resource "scalingo_project" "test-project" { - name = "test-project" - default = true - } - ``` - -## Updating a project - -Two attributes can be updated: `name` and `default`. - -{% note %} - `default` cannot be changed from true to false. To change the default project, update an existing project to be the new default one, or create a new default project. -{% endnote %} - -### Using the Dashboard - -1. From your web browser, open your [dashboard][dashboard] -2. Click the **Apps** tab -3. Click on the application for which you want to edit the project -4. Click the **Settings** tab, make sure to select **General** -5. Click **`your-project` settings** (where `your-project` is the current name of the project you want to edit) -6. Edit either the `name` of the project or tick the checkbox to make it the `default` project or update both -7. Click **Edit** - -### Using the Command Line - -1. Make sure you have correctly [setup the Scalingo command line tool][cli] -2. From the command line, update a project name: - ```shell - scalingo projects-update --name=updated-test-project prj-6731a609-02b6-4614-b28d-5abe43654333 - ``` - The output should look like this: - ```shell - -----> test-project has been updated - ``` - You can also update a project to become the new default: - ```shell - scalingo projects-update --default prj-6731a609-02b6-4614-b28d-5abe43654333 - ``` - -### Using the Terraform Provider - -There is only one step required to update a project using Terraform. You need to -update the project with the desired attributes. For example: - ```tf - resource "scalingo_project" "test-project" { - name = "updated-test-project" - } - ``` - -## Removing a project - -A project can be removed only if this is not the default one, and no application is linked to it. - -### Using the Dashboard - -This feature is not yet available in the dashboard. - -### Using the Command Line - -1. Make sure you have correctly [setup the Scalingo command line tool][cli] -2. From the command line, update a project: - ```shell - scalingo projects-remove prj-6731a609-02b6-4614-b28d-5abe43654333 - ``` - The output should look like this: - ```shell - -----> prj-6731a609-02b6-4614-b28d-5abe43654333 has been removed - ``` - -### Using the Terraform Provider - -There is only one step required to remove a project using Terraform. You just need to -remove the associated resource from the Terraform file. - -[dashboard]: https://dashboard.scalingo.com/ - -[cli]: {% post_url platform/cli/2000-01-01-start %} -[projects-overview]: {% post_url platform/projects/2000-01-01-overview %} diff --git a/src/_posts/platform/projects/2000-01-01-overview.md b/src/_posts/platform/projects/2000-01-01-overview.md deleted file mode 100644 index aa725376b..000000000 --- a/src/_posts/platform/projects/2000-01-01-overview.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Projects Overview -modified_at: 2025-09-09 07:00:00 -tags: project overview -index: 1 ---- - -Projects offer a new way to organize your applications and resources. They let you group applications into logical units that reflect your organization's structure: by product, customer, environment, or any other approach that fits your needs. - -{% note %} -**Today** projects are flexible: applications can still be moved or regrouped freely. - -Starting **March 1, 2026**, projects will become a core structural element of the Scalingo platform. This means that applications will no longer be movable between projects, and projects themselves will serve as the foundation for future platform features. -{% endnote %} - -{% warning %} -We strongly recommend grouping your applications into projects before **March 1, 2026**. After this date, applications can no longer be regrouped or moved between projects, except by recreating them in the target project. -{% endwarning %} - -[Learn how to manage your projects][project-management-page]. - -## Why use Projects? - -Projects provide a structured way to separate applications according to your own logic, -whether by product, customer, environment, or any other approach that fits your needs. This makes large accounts easier to navigate and manage, while keeping resources clearly organized. - -In the near future, Projects will also become the cornerstone of application billing, advanced access controls, and network-related security features. Private networks are one of the upcoming capabilities that will build on top of Projects. By starting to group your applications into Projects today, you ensure that your organization is ready to take full advantage of these future improvements. - -## Default Project - -The project named **default** is created automatically when your account is set up. By default, this project is used for any application or resource that is not explicitly assigned to another project. You can rename this project at any time, or designate any of your other projects as the new default one to better match your organization's needs. - -## Current Limitations - -- Currently, only the owner of a project or an app can move an application between projects. -- Projects cannot be deleted from the Dashboard, they can be [removed using the CLI, API or Terraform][removing-project]. -- Collaborators may not see all applications within a project. They only see the applications to which they have been individually added. User management remains at the application level for now, until more granular access controls are introduced at the organizational and project levels. -- Accounts are limited to 20 projects to prevent misuse. This limit can be raised depending on your needs by contacting our support team. - -## Transition Timeline - -We are introducing a transition period with clear milestones: - -- September 1, 2025: all existing resources have automatically been assigned to a Project named **default**. -- September 15, 2025: start of the transition period with the introduction of Projects. At this stage, projects remain flexible, and applications can still be regrouped freely. -- Ahead of March 1, 2026: new interfaces and management capabilities will be introduced to strengthen the role of Projects as a core element of the platform and improve the overall experience. -- By March 1, 2026: Projects will become a fixed and foundational component of the platform. From this date, applications can no longer be regrouped between projects. -- After this date, moving a single application from one project to another will no longer be possible. Changing a project for an application will require recreating and redeploying it in the target project. - -{% warning %} -We strongly recommend grouping your applications into projects before the deadline to ensure a smooth transition as they become a core element of the Scalingo platform. -{% endwarning %} - -[project-management-page]: {% post_url platform/projects/2000-01-01-manage-projects %} -[removing-project]: {% post_url platform/projects/2000-01-01-manage-projects %}#removing-a-project diff --git a/src/changelog/features/_posts/2025-09-08-projects.md b/src/changelog/features/_posts/2025-09-08-projects.md deleted file mode 100644 index 86254b936..000000000 --- a/src/changelog/features/_posts/2025-09-08-projects.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -modified_at: 2025-09-11 07:00:00 -title: 'Introducing Projects' ---- - -We are introducing **[Projects]({% post_url platform/projects/2000-01-01-overview %})** to help you organize and structure your applications more effectively. - -Projects provide a flexible way to group your applications according to your own logic: by product, customer, environment, or any other approach that fits your needs. This makes large accounts easier to navigate and manage, while keeping resources clearly separated. - -Over time, Projects will evolve into a **core building block of the Scalingo platform**, serving as the foundation for new features in billing, access management, and network security. One of the upcoming capabilities will be **Private Networks**, enabling applications within the same project to communicate securely in an isolated environment. - -👉 [Learn how to get started with Projects]({% post_url platform/projects/2000-01-01-overview %})