feat: npm command for resetting DB

Usage: "npm run reset:db"

Author: maxceem

README.md

@@ -20,7 +20,7 @@ tc-notifications (as a standard nodejs app) provides generic framework around no
 5. Either add deployment for this new notification consumer/processor in existing deployment script (if you want to host the processor as separate service in the same ECS cluster) or write a new script if you want to keep the deployment separate.
 
 ## Dependencies
-- nodejs https://nodejs.org/en/ (v6+, if newer version of node is used, e.g. v10, then it needs to install extra lib `npm i natives@1.1.6` to support the gulp build)
+- nodejs https://nodejs.org/en/ (v6+, if newer version of node is used, e.g. v10, then it needs to install extra lib `npm i natives@1.1.6` to support the gulp build)
 - Heroku Toolbelt https://toolbelt.heroku.com
 - git
 - PostgreSQL 9.5
@@ -50,8 +50,8 @@ The following parameters can be set in config files or in env variables:
       if not provided, then SSL connection is not used, direct insecure connection is used;
       if provided, it can be either path to private key file or private key content
 - **Topcoder API**
-  - `TC_API_V3_BASE_URL`: the TopCoder API V3 base URL
-  - `TC_API_V4_BASE_URL`: the TopCoder API V4 base URL
+  - `TC_API_V3_BASE_URL`: the TopCoder API V3 base URL
+  - `TC_API_V4_BASE_URL`: the TopCoder API V4 base URL
   - `TC_API_V5_BASE_URL`: the TopCoder API V5 base URL
 - **Notifications API**
   - `API_CONTEXT_PATH`: path to serve API on
@@ -61,16 +61,16 @@ The following parameters can be set in config files or in env variables:
   - `TOKEN_CACHE_TIME`: time period of the cached token
   - `AUTH0_CLIENT_ID`: auth0 client id
   - `AUTH0_CLIENT_SECRET`: auth0 client secret
-  - `AUTH0_PROXY_SERVER_URL`: auth0 proxy server URL
-- **Consumer handlers**
-  - `KAFKA_CONSUMER_HANDLERS`: mapping from consumer topic to handlers
-- **Email notification**
-  - `ENV`: used to construct email category
-  - `ENABLE_EMAILS`: whether to enable email notifications
-  - `ENABLE_DEV_MODE`: whether to enable dev mode
-  - `DEV_MODE_EMAIL`: recipient email used in dev mode
-  - `DEFAULT_REPLY_EMAIL`: default reply email
-
+  - `AUTH0_PROXY_SERVER_URL`: auth0 proxy server URL
+- **Consumer handlers**
+  - `KAFKA_CONSUMER_HANDLERS`: mapping from consumer topic to handlers
+- **Email notification**
+  - `ENV`: used to construct email category
+  - `ENABLE_EMAILS`: whether to enable email notifications
+  - `ENABLE_DEV_MODE`: whether to enable dev mode
+  - `DEV_MODE_EMAIL`: recipient email used in dev mode
+  - `DEFAULT_REPLY_EMAIL`: default reply email
+
 
 ### Connect notification server
 Configuration for the connect notification server is at `connect/config.js`.
@@ -137,6 +137,7 @@ You may reuse it during review.
 - start local PostgreSQL db, create an empty database, update the config/default.js DATABASE_URL param to point to the db
 - install dependencies `npm i`
 - run code lint check `npm run lint`
+- init DB `npm run reset:db`
 - start connect notification server `npm start`
 - the app is running at `http://localhost:4000`, it also starts Kafka consumer to listen for events and save unroll-ed notifications to db
 

package.json

@@ -11,7 +11,8 @@
     "lint:fix": "eslint *.js --fix src config test connect",
     "postinstall": "npm run build",
     "build": "gulp build",
-    "watch": "gulp watch"
+    "watch": "gulp watch",
+    "reset:db": "node tools/resetDb.js"
   },
   "author": "TCSCODER",
   "license": "none",

tools/resetDb.js

@@ -0,0 +1,20 @@
+/**
+ * Script for initializing/resetting DB.
+ *
+ * WARNING
+ * It recreates DB schema causing removing existent data if any.
+ */
+const notificationServer = require('../index');
+
+console.info('Initializing db...');
+
+notificationServer
+  .initDatabase()
+  .then(() => {
+    console.info('Database was successfully initialized.');
+    process.exit();
+  })
+  .catch((err) => {
+    console.error('Error initializing DB', err);
+    process.exit(1);
+  });