depau/HackMD
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Update install instructions to cover sequelize

Browse source 
We instruct people to run db migrations on inital setup. We should do
that!

Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
This commit is contained in:
Sheogorath 2018-06-26 22:56:05 +02:00
parent 6218c703a9
commit 3b9e29a14a
No known key found for this signature in database
GPG key ID: 1F05CC3635CDDFFD
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -80,7 +80,10 @@ Just to more confusion: We are still friends with HackMD :heart:
3. Setup the configs, see more below 3. Setup the configs, see more below
4. Setup environment variables which will overwrite the configs 4. Setup environment variables which will overwrite the configs
5. Build front-end bundle by `npm run build` (use `npm run dev` if you are in development) 5. Build front-end bundle by `npm run build` (use `npm run dev` if you are in development)
6. Run the server as you like (node, forever, pm2) 6. Modify the file named `.sequelizerc`, change the value of the variable `url` with your db connection string
For example: `postgres://username:password@localhost:5432/codimd`
7. Run `node_modules/.bin/sequelize db:migrate`, this step will migrate your db to the latest schema
8. Run the server as you like (node, forever, pm2)
## Heroku Deployment ## Heroku Deployment