dashboard project names could be confusing about strapi

[Aurelsicoko]

Each application connected to the Strapi Studio has a unique identifier. This identifier is available in the ./config/global.json file. We could display it before the project name?

[loicsaintroch]

I have a question about forcing users to use unique app names. Do you think about a unique name like an identifier for every app of every user juste like Heroku do? Or a unique app name by user?

[Aurelsicoko]

@loicsaintroch A unique name for every app of every user would mean that the CLI $ strapi new <appName> should return an error in case this name already exists?

[loicsaintroch]

A unique identifier is the best way, just like Heroku does.

Either the user does $ strapi new and the Strapi Studio defines a unique and unused identifier for the app. Or the user defines a name with $ strapi new <appName> and the Strapi Studio returns an error if the name (identifier) is already taken. In both solutions, an Internet access is needed, which sucks...

There are some tricky use cases: no Internet access, Studio connection disabled, etc.

[Aurelsicoko]

I think our current solution is the best. We already have a unique identifier. In my opinion, this is an user experience problem, not a technical problem.

We can't require an Internet access. If the Strapi Studio connection failed for many reasons, we have to create another command $ strapi init to identify this project with the Strapi Studio. This will return and give an identifier to the project.

Moreover this command could be very interesting to change and get a new identifier for a project. Currently, we have to create a new app with the existing CLI $ strapi new <appName> and copy the files into it to change our identifier.

[loicsaintroch]

Agreed.

[ogrotten]

It is a UX problem, to be sure.

I think a simple solution which doesn't change the current method at all would be to show the creation date on the dash right there with the project name. This doesn't require extra access as the date is on the package.json file.

strapi init could also contain a number of commands for general maintenance of a project... regenerating the secret key, renaming the proj, perhaps even more involved things like changing the database. Seems like feasibly an entire wing of the whole strapi project.

[Aurelsicoko]

I added the unique identifier next to the app name, and also the creation date to be sure there is no confusion. You will see those changes in the next release.

[loicsaintroch]

We'll definitely create a $ strapi init command for the next release.

Thank you @ogrotten!