Rename a project
What this page is for. Change the name this panel shows for a project — and know where the name your customers see actually comes from, because it is not here.
You need
- The panel open, on the Projects page (in the Panel menu group).
The two names every project has
Every project on this server carries two names, and only one of them can be changed.
| Name | Example | Can it change? |
|---|---|---|
| Project name — the label in this panel | Grocery Two | yes, on this page |
| Short id — what the server uses | shop2 | no, ever |
The short id is written into the name of the project's Linux user, its PHP worker pool, its database, its systemd units, its web-server files and the folder your code sits in. Renaming it would mean rebuilding all of that, so the panel does not offer it. Pick it carefully when you create a project — see More than one project.
What the project name is used for
One thing: the name shown in this panel and in the project switcher, so you can tell your projects apart. That is all it is.
It is not the name your customers see. Your shop's public name — the one on the storefront, on invoices and in your emails — is set inside 6ammart's own admin panel, under its business settings. Change it there and it changes everywhere your customers look. Renaming the project here does not touch it.
Rename it
- Open Projects.
- On the project's card, press rename….
- Type the new name. Up to 60 characters.
- Press Rename the project.
It takes effect at once. There is no job to wait for.
What does not change
Everything except the label:
- The short id, and therefore the Linux user, the PHP pool, the database name, the database contents, the systemd units, the web-server files and the folder your code lives in.
- Your domains and your certificates.
- Your backups.
- Anything inside the app: your business name, your logo, your email templates and the browser-tab title are all 6ammart's own settings and are not touched by this.
- Nobody is signed out. Nothing restarts. Your site keeps serving customers right through the rename.
The app's own APP_NAME setting
The 6ammart app has a setting called APP_NAME in its .env file. The panel
never writes it. On a project installed through 6ammart's own web installer it
usually reads something like 6amMart1786172740, and leaving it that way is
fine — customers never see it.
It is not cosmetic underneath. Laravel builds the login-cookie name from it, so changing it signs everyone out — staff and customers. That is why a project rename does not touch it, and why nothing in the panel changes it on your behalf.
Laravel also used to build the cache and Redis key names from it, which meant
6ammart's own "update the software" step — which rewrites APP_NAME every time
it runs — emptied your cache and signed everyone out as a side effect. The panel
now owns those two key names instead, so a software update no longer takes your
cache and your sessions with it.
If you really do want to change it, you can, by hand: App .env →
APP_NAME. The field is editable, the same warning is printed next to it, and
the page asks you to confirm before it saves. Nothing is deleted and no order is
lost — people simply log in again — but do it in a quiet hour, not during your
busiest one.
How to check it worked
- Projects shows the new name on the card, and the project switcher uses it.
- Your site is unchanged: same page title, same cookies, nobody logged out.
If it went wrong
- "project name is required" — the box was empty, or the name was made only of characters the panel strips (
$,,\,"` and control characters). Type a plain name. - "project name must be 60 characters or fewer" — shorten it.
- The name on the card did not change — reload the page. If it is still the old one, the save was refused; the reason is on the Activity log on the Security page.