Renamed the folder to drop the dash. Every command now stops at:
✖ CONFIG_INVALID: Project slug "demo-shop" does not match its directory "demoshop".
hint: Rename the directory to demo-shop or set slug: demoshop.
docs: https://docs.sdods.com/docs/guides/configurationI can obviously do either. Which one is the right one, and why does it care at all?
Accepted answer
Change whichever one is wrong and leave the other alone — the point of the check is that there is only ever one name.
The slug is the identity everything else addresses the project by: -p demo-shop on every command, the folder discovery walks, the run target names, the artefact paths. If the folder and the yaml could disagree, half of those would resolve one way and half the other, and the failure would land somewhere unrelated hours later. So the two are compared the moment the project file is parsed.
If you actually want the new name, rename both and update the references:
git mv projects/demoshop projects/demo-shopSlugs are lowercase letters, digits and dashes.
One thing to check before you settle on a new slug: anything that already stored runs under the old one keeps them there. We renamed a project and then spent an afternoon wondering where the history went. Not a blocker, just do it deliberately rather than as a drive-by tidy-up.
Have the same question?
Ask it with the command you ran and the output you got, and it will be answered here.
Ask a question