From e5c31b7171edc29341193b2e37bce276badbaf83 Mon Sep 17 00:00:00 2001 From: Edward Kim Date: Mon, 18 Mar 2019 17:02:19 -1000 Subject: [PATCH] Update README to reflect latest changes --- README.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 69f4507..bf4d86f 100644 --- a/README.md +++ b/README.md @@ -10,10 +10,6 @@ Use `npm run start` to start the react server ` The above configurations tells the react proxy server to redirect all api calls to the backend docker instance. The `nodemonConfig` tells nodemon to only watch the server dir. -The way the knexfile is setup, the development section allow the user to run the knex migration from the host computer and is routed to the docker instance using localhost. The production section is used by docker to setup the postgres DB and it's connections to the rest of the docker containers. +The way the knexfile is setup, there is a single configuration shared by both development and production. -This is controlled using the `ENVIRONMENT` property within the docker-compose.override.yml file, under the environment section. - -`knex migrate:latest` will run any migrations made, but this needs to be run in the server dir as that is where the knexfile.js is. - -The `npm run dev` script within the package.json file sets up the how docker is going to run the express server using nodemon. +Migrations and Seeds are now run automatically on launching the express docker container via the deploy-*.js files. It also launches the server with node in production mode or launches nodemon watching all files in development mode.