StyAndCo/zeppelin
3
0
Fork 0
mirror of https://github.com/ZeppelinBot/Zeppelin.git synced 2025-05-21 16:55:03 +00:00
Code Releases Activity

Switch to auto-ordering lists

Browse source 
Co-authored-by: Almeida <almeidx@pm.me>
This commit is contained in:
Bluenix 2021-08-15 20:58:20 +02:00 • committed by GitHub
parent 7d65a6a678
commit aa41b358be
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -32,20 +32,20 @@ These instructions are intended for bot development only, they are not recommend
1. Go into the backend directory: `cd backend` 1. Go into the backend directory: `cd backend`
2. Install dependencies: `npm ci` 1. Install dependencies: `npm ci`
3. Make a copy of `bot.env.example` and `api.env.example` (removing the `.example` suffix), fill in the values. 1. Make a copy of `bot.env.example` and `api.env.example` (removing the `.example` suffix), fill in the values.
There are defaults for your convenience, feel free to replace these. There are defaults for your convenience, feel free to replace these.
4. Setup the database: `npm run migrate-dev` 1. Setup the database: `npm run migrate-dev`
5. To start the backend, there are two alternatives: 1. To start the backend, there are two alternatives:
- **It is recommended** to use `npm run watch` for development. This will automatically restart on save - **It is recommended** to use `npm run watch` for development. This will automatically restart on save
- Run `npm run build` followed by the desired start script: - Run `npm run build` followed by the desired start script:
- `npm run start-bot-dev` to start the bot. - `npm run start-bot-dev` to start the bot.
- `start-api-dev` to start the api server. - `start-api-dev` to start the api server.
6. On the first run the bot will attempt to add all IDs from `STAFF` in `api.env` into the database 1. On the first run the bot will attempt to add all IDs from `STAFF` in `api.env` into the database
### Running the dashboard ### Running the dashboard