Merge pull request #36 from mnfst/openapi

doc: adapt to new npm scripts

Author: brunobuddy

config.md

@@ -107,5 +107,5 @@ The backend fits in an [NPM Package](https://www.npmjs.com/package/manifest) tha
 If you plan to run Manifest on a **mounted drive** like most cloud editors do, add the `--mountedDrive` argument to the run command to prevent [watcher errors](https://github.com/remy/nodemon?tab=readme-ov-file#application-isnt-restarting):
 
 ```
-npm run manifest -- --mountedDrive
+npm run start -- --mountedDrive
 ```

deploy.md

@@ -65,7 +65,7 @@ See more [environment variables](./config.md#general-variables) you may need.
 
 ### Start script for production
 
-The `npm run manifest` script should only be used for **development** as it watches file changes.
+The `npm run start` script should only be used for **development** as it watches file changes.
 
 Go back to your codebase and open the `package.json` file and add a new **start** script on the scripts list with the value `node node_modules/manifest/dist/manifest/src/main.js` as following:
 

entities.md

@@ -39,7 +39,7 @@ You can now add your own pets through the admin panel!
 To generate dummy data for all your entities, run the simple command:
 
 ```
-npm run manifest:seed
+npm run seed
 ```
 
 :::warning
@@ -95,7 +95,7 @@ ContactPage:
 You can generate dummy data for all your entities with the simple command:
 
 ```
-npm run manifest:seed
+npm run seed
 ```
 
 ### Entity params

introduction.md

@@ -55,7 +55,7 @@ To start the Manifest backend, run the following command in the new project fold
 
 ```
 cd my-project
-npm run manifest
+npm run start
 ```
 
 You can now: