ti2 1.0.13 → 1.0.16

package/.github/workflows/tests.yml

@@ -1,8 +1,6 @@
 name: Tests Workflow
 
-on:
-  workflow_dispatch:
-  push:
+on: [workflow_dispatch, push, pull_request]
 
 jobs:
   test:

package/README.md

@@ -22,21 +22,9 @@ App Plugins are value added tools that only speak to Ti2 and other plugins. For
 
 Ti2 can be deployed on your own servers, or you can connect to a Ti2 instance that another company is hosting.
 
-### Security
-
-An admin api key is set trough an environment variable called adminKey; using this API key is possible to create Users and/or application authentications.
-
-A new User / User Authentication can be created using the endpoint [createUserToken](https://ti2.tourconnect.dev/api-docs/#/admin/createUserToken); the return value consists of a JWT token for further user intraction with the App; the admin API key is required; no password is saved on the server side.
-
-Apps / Integrations can be created using the admin API Key; this after the plugin had been added to the codebase; the app can be created using the endpoint [createApp](https://ti2.tourconnect.dev/api-docs/#/admin/createApp); such endpoint returns a key that can be used by the app to interact with user Ids; such interactions allow the app to push for changes related to user integrations, the app can list the users currently configured for it using the endpoint [listAppTokens](https://ti2.tourconnect.dev/api-docs/#/app/listAppTokens); the passwords for Apps are encripted onde the database using aes-256-cbc, more details can be found on the [``models/integrations.js``](https://github.com/ti2travel/ti2/blob/main/models/integration.js) file.
-
-User + app integration credentials can be added after the app has been added to the system; these can be added by either the user, admin or the app itself using the endpoint [createAppToken](https://ti2.tourconnect.dev/api-docs/#/app/createAppToken). These keys are saved in JWT format on the database.
-
 ## Getting Started
 
-You can start follow [this guide]{@tutorial setup-your-instance} to create an instance, if you want to add an integration (like for your own backend) or add a new internal funtionality you can [create a plugin]{@tutorial plugin-development} for your system.
-
-By default a ti2 instance serves a documentation page on the url (http://[yourinstance]/api-docs/) that serves the available API restfull methods, you can review the [swagger documentation page online](https://ti2-staging.tourconnect.com/api-docs/) .
+You can write your [own plugin]{@tutorial plugin-development} that hooks up to a Ti2 instance or you can run a server that that hosts your [own **Ti2** instance]{@tutorial setup-your-instance} with any plugins (your own or from the plugin library).
 
 
 ## Plugins

package/api.yml

@@ -816,6 +816,97 @@ paths:
             application/json:
               schema:
                 $ref: '#/components/schemas/bookingsProductSearchReturn'
+  /bookings/{appKey}/{userId}/availabilitycalendar:
+    post:
+      security:
+        - bearerAuth: ['admin', 'user']
+      tags:
+        - bookings
+      summary: Availability Search
+      operationId: bookingsAvailabilityCalendar
+      parameters:
+        - name: appKey
+          in: path
+          description: app to search availability for, defaults to first token
+          required: true
+          example: 'travelgate-hotelx'
+          schema:
+            type: string
+        - name: userId
+          in: path
+          description: the user/company that the appKey belongs to
+          required: true
+          schema:
+            type: string
+      requestBody:
+        description: both app details
+        required:  true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AnyValue'
+      responses:
+        '200':
+          description: search results
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  availability:
+                    type: array
+                    required: true
+                    items:
+                      $ref: '#/components/schemas/availabilityItem'
+  /bookings/{appKey}/{userId}/{hint}/availabilitycalendar:
+    post:
+      security:
+        - bearerAuth: ['admin', 'user']
+      tags:
+        - bookings
+      summary: Availability Search for an specific hint
+      operationId: bookingsAvailabilityCalendar
+      parameters:
+        - name: appKey
+          in: path
+          description: app to search availability for, defaults to first token
+          required: true
+          example: 'travelgate-hotelx'
+          schema:
+            type: string
+        - name: userId
+          in: path
+          description: the user/company that the appKey belongs to
+          required: true
+          schema:
+            type: string
+        - name: hint
+          in: path
+          description: a specific token hint to be used
+          required: true
+          example: 'travelgate-australia'
+          schema:
+            type: string
+      requestBody:
+        description: both app details
+        required:  true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AnyValue'
+      responses:
+        '200':
+          description: search results
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  availability:
+                    type: array
+                    required: true
+                    items:
+                      $ref: '#/components/schemas/availabilityItem'
   /bookings/{appKey}/{userId}/availability:
     post:
       security:

package/cli.js

@@ -0,0 +1,36 @@
+#!/usr/bin/env node
+
+const { Command, Argument } = require('commander');
+
+const { migrateApp } = require('./controllers/app');
+const { migrate } = require('./controllers/admin');
+
+const program = new Command();
+
+program
+  .name('ti2-cli')
+  .description('TI2 Command line interface utilities')
+  .version((require('./package.json')).version);
+
+program.command('dbapp')
+  .description('Handle database migrations for apps')
+  .argument('<string>', 'integration to operate on')
+  .addArgument(
+    new Argument('<action>', 'action to take', 'migrate')
+      .choices(['migrate', 'revert']),
+  )
+  .action(async (integration, action) => {
+    await migrateApp({ integrationId: integration, action });
+  });
+
+program.command('db')
+  .description('Handle database migrations for integrations')
+  .addArgument(
+    new Argument('<action>', 'action to take', 'migrate')
+      .choices(['migrate', 'revert']),
+  )
+  .action(async action => {
+    await migrate({ action });
+  });
+
+program.parse();

package/controllers/admin.js

@@ -1,6 +1,11 @@
 const jwt = require('jsonwebtoken');
 const assert = require('assert');
 const { omit } = require('ramda');
+const { Umzug, SequelizeStorage } = require('umzug');
+const Sequelize = require('sequelize');
+const fs = require('fs').promises;
+const path = require('path');
+
 const sqldb = require('../models');
 
 const { env: { jwtSecret } } = process;
@@ -91,10 +96,50 @@ const resetIntegrationToken = async (req, res, next) => {
   }
 };
 
+const migrate = async ({ action }) => {
+  const { sequelize } = sqldb;
+  const migrationsPath = path.join(
+    __dirname,
+    '../',
+    'migrations',
+  );
+  try {
+    await fs.access(migrationsPath);
+  } catch (err) {
+    throw Error(`Could not find any migrations on ${migrationsPath}`);
+  }
+  const umzug = new Umzug({
+    migrations: {
+      glob: `${migrationsPath}/*.js`,
+      resolve: ({ name, path: migPath, context }) => {
+        const migration = require(migPath);
+        return {
+          name,
+          up: async () => migration.up(context, Sequelize),
+          down: async () => migration.down(context, Sequelize),
+        };
+      },
+    },
+    context: sequelize.getQueryInterface(),
+    storage: new SequelizeStorage({
+      sequelize,
+    }),
+    logger: console,
+  });
+  if (action === 'migrate') {
+    return umzug.up();
+  }
+  if (action === 'revert') {
+    return umzug.down({ to: 0 });
+  }
+  throw Error('No recognized action');
+};
+
 module.exports = {
   createApp,
-  deleteApp,
   createUserToken,
+  deleteApp,
   listApps,
+  migrate,
   resetIntegrationToken,
 };

package/controllers/app.js

@@ -1,5 +1,11 @@
 const jwt = require('jwt-promise');
 const { omit } = require('ramda');
+const assert = require('assert');
+const { Umzug, SequelizeStorage } = require('umzug');
+const path = require('path');
+const Sequelize = require('sequelize');
+const fs = require('fs').promises;
+
 const sqldb = require('../models');
 
 const { env: { jwtSecret } } = process;
@@ -83,9 +89,54 @@ const listAppTokens = async (req, res, next) => {
   }
 };
 
+const migrateApp = async ({ integrationId, action }) => {
+  const { sequelize } = sqldb;
+  assert(integrationId);
+  assert(action);
+  const migrationsPath = path.join(
+    __dirname,
+    '../',
+    '../',
+    `ti2-${integrationId}`,
+    'migrations',
+  );
+  try {
+    await fs.access(migrationsPath);
+  } catch (err) {
+    throw Error(`Could not find any migrations for ${integrationId} on ${migrationsPath}`);
+  }
+  const umzug = new Umzug({
+    migrations: {
+      glob: `${migrationsPath}/*.js`,
+      resolve: ({ name, path: migPath, context }) => {
+        const migration = require(migPath);
+        return {
+          name,
+          up: async () => migration.up(context, Sequelize),
+          down: async () => migration.down(context, Sequelize),
+        };
+      },
+    },
+    context: sequelize.getQueryInterface(),
+    storage: new SequelizeStorage({
+      sequelize,
+      tableName: `SequelizeMeta-${integrationId}`,
+    }),
+    logger: console,
+  });
+  if (action === 'migrate') {
+    return umzug.up();
+  }
+  if (action === 'revert') {
+    return umzug.down({ to: 0 });
+  }
+  throw Error('No recognized action');
+};
+
 module.exports = {
-  jwtEncode,
   createAppToken,
   deleteAppToken,
+  jwtEncode,
   listAppTokens,
+  migrateApp,
 };

package/controllers/bookings.js

@@ -110,6 +110,33 @@ const bookingsAvailabilitySearch = plugins => async (req, res, next) => {
   }
 };
 
+const bookingsAvailabilityCalendar = plugins => async (req, res, next) => {
+  const {
+    params: { appKey, userId, hint },
+    body: payload,
+  } = req;
+  try {
+    const app = plugins.find(({ name }) => name === appKey);
+    // const app = load(appKey);
+    const userAppKeys = (await UserAppKey.findOne({
+      where: {
+        userId,
+        integrationId: appKey,
+        ...(hint ? { hint } : {}),
+      },
+    }));
+    assert(userAppKeys, 'could not find the app key');
+    const token = userAppKeys.appKey;
+    const results = await app.availabilityCalendar({
+      token,
+      payload,
+    });
+    return res.json(results);
+  } catch (err) {
+    return next(err);
+  }
+};
+
 const searchQuote = plugins => async (req, res, next) => {
   const {
     params: { appKey, userId, hint },
@@ -171,6 +198,7 @@ module.exports = plugins => ({
   bookingsCancel: bookingsCancel(plugins),
   bookingsProductSearch: bookingsProductSearch(plugins),
   bookingsAvailabilitySearch: bookingsAvailabilitySearch(plugins),
+  bookingsAvailabilityCalendar: bookingsAvailabilityCalendar(plugins),
   searchQuote: searchQuote(plugins),
   createBooking: createBooking(plugins),
 });

package/jsdoc.conf.json

@@ -13,7 +13,10 @@
     ],
     "templates": {
         "cleverLinks": true,
-        "monospaceLinks": true
+        "monospaceLinks": true,
+        "default": {
+            "includeDate": false
+        }
     },
     "opts": {
         "destination": "docs",

package/models/db.js

@@ -7,7 +7,6 @@ const {
 } = process;
 
 const options = {
-  operatorsAliases: false,
   logging: false,
 };
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ti2",
-  "version": "1.0.13",
+  "version": "1.0.16",
   "description": "Tourist Industry Exchange (TI2)",
   "main": "index.js",
   "scripts": {
@@ -12,6 +12,7 @@
     "type": "git",
     "url": "git+https://github.com/ti2travel/ti2.git"
   },
+  "bin": "./cli.js",
   "author": "",
   "license": "GPL-3",
   "bugs": {
@@ -20,6 +21,7 @@
   "homepage": "https://github.com/ti2travel/ti2#readme",
   "dependencies": {
     "bluebird": "^3.7.2",
+    "commander": "^9.2.0",
     "express": "^4.17.2",
     "js-yaml": "^4.1.0",
     "jsonwebtoken": "^8.5.1",
@@ -32,6 +34,7 @@
     "swagger-express-middleware": "3.0.0-alpha.5",
     "swagger-routes-express": "3.3.1",
     "swagger-ui-express": "4.3.0",
+    "umzug": "^3.1.1",
     "uninstall": "^0.0.0"
   },
   "devDependencies": {

package/test/plugin.js

@@ -3,7 +3,7 @@ const chance = require('chance').Chance();
 
 class Plugin {
   /**
-   * For a comprehensive list of mehtods visit the
+   * For a comprehensive list of methods visit the
    * [Plugin Development]{@tutorial plugin-development} page.
    *
    * ---
@@ -46,11 +46,11 @@ class Plugin {
   }
 
   /**
-   *  Check the vailidity of an integration token.
+   *  Check the validity of an integration token.
    * @async
    * @param {Object} args - Availability search arguments.
    * @param {Object} args.token - A token definition, it's content varies between integrations.
-   * @returns {Boolean} - The token vailidity True/False
+   * @returns {Boolean} - The token validity True/False
    */
   validateToken() {
     return Boolean(this);
@@ -306,7 +306,7 @@ class Plugin {
    * @param {string} args.payload.travelDateEnd - Date of travel end.
    * @param {Holder} args.payload.holder - Search for a particular holder.
    * @returns {object} retVal - the return object.
-   * @returns {Booking[]} retVal.bookings - Array of Bookings matchin the criteria.
+   * @returns {Booking[]} retVal.bookings - Array of Bookings matching the criteria.
    */
   searchBooking() {
   }
@@ -363,7 +363,22 @@ class Plugin {
   searchAvailability() {
     // return (args);
   }
-
+  /**
+   * Retrieve an availability calendar over a date range
+   * @async
+   * @param {Object} args - Availability search arguments.
+   * @param {Object} args.token - A token definition, it's content varies between integrations.
+   * @param {Object} args.payload - Search spect object.
+   * @param {string} args.payload.dateFormat - Date format sent, using [momentjs formatting](https://momentjs.com/docs/#/parsing/string-format/).
+   * @param {string} args.payload.travelDateStart - Date of travel start.
+   * @param {string} args.payload.travelDateEnd - Date of travel end.
+   * @param {Occupancy[]} args.payload.occupancies - Occupancy detail.
+   * @returns {object} retVal - the return object
+   * @returns {Availability[]} retVal.availability - Array of availability objects
+   */
+  availabilityCalndar() {
+    // return (args);
+  }
   /**
    * A quote return spec
    * @typedef {Object} Quote

package/tutorials/index.json

@@ -1,6 +1,6 @@
 {
     "setup-your-instance": {
-        "title": "Setting up your instancce"
+        "title": "Running your own Ti2"
     },
     "plugin-development": {
         "title": "Plugin Development"

package/tutorials/plugin-development.md

@@ -1,21 +1,15 @@
-## Environment values
+## Getting Started
 
-Plugin environment keys are passed down to the instance while is being created, this is the preferred way of accesing environmen keys from the plugins, such values are not design to hold client / user's API keys or specific data, they are to be stored on the database itself via the AppKey collection.
+Plugins can extend the functionality of Ti2 and/or provide access to other platforms; you should use one of the following methods to provide a stadandarized way to access other systems; if you want to implement new functionality that is not encompassed on the available methods you are more than welcome to add new methods and contribute to the Ti2 codebase.
 
-Plugin ENV variable name convention: ti2_pluginName_environmenVariableName, for example:
-
-```env
-ti2_tourconnect_apiUrl=http://backend:8080
-```
-
-## Methods
+## Available Methods
 
-In oorder for an integration or system apps, we must use a set of standirzed methods to matain a compatibility; there are following methods are available, more can be supported but should be a part of the API TI2 spec to maximize it's compatibility.
+We are using a set of standardized methods to maintain compatibility; the following methods are available, more can be supported but should be a added to the TI2 spec first to maximize it's compatibility.
 
 **General Methods** (should always be included):
 * [validateToken]{@link Plugin#validateToken}
 
-**Content Methods** (related to marketing information update for profile, locations and/or products):
+**Content Methods** (marketing information for (company)profile, locations and/or products):
 * [getProfile]{@link Plugin#getProfile}
 * [updateProfile]{@link Plugin#updateProfile}
 * [createLocation]{@link Plugin#createLocation}
@@ -24,7 +18,7 @@ In oorder for an integration or system apps, we must use a set of standirzed met
 * [createProduct]{@link Plugin#createProduct}
 * [updateProduct]{@link Plugin#updateProduct}
 
-**Booking Methods** (all related to bookings and operations):
+**Booking Methods** (bookings and operations):
 * [searchBooking]{@link Plugin#searchBooking}
 * [searchProducts]{@link Plugin#searchProducts}
 * [searchAvailability]{@link Plugin#searchAvailability}
@@ -33,10 +27,20 @@ In oorder for an integration or system apps, we must use a set of standirzed met
 
 ---
 
+## Environment variables
+
+Plugin environment keys are passed down from the hosting ti2 instance when they are generated, this is the preferred way to access environment keys from the plugins, such values are not design to hold client / user's API keys or specific data, they are to be stored in the database via the AppKey collection.
+
+Plugin ENV variable name convention: ti2_pluginName_environmenVariableName, for example:
+
+```env
+ti2_tourconnect_apiUrl=http://backend:8080
+```
+
 
 ## Codebase setup
 
-You can review some of the plugins previously developed and use them as a guide, plugin methods are encourage to include tests and return results on the same format, however the return values can include additional information, currently Ti2 is expected to run on node version 12.22.8; we suggest you use the same for your codebase.
+You can review some of the plugins previously developed and use them as a guide, plugin methods are encourage to include tests and to return results with the same format; however, the returned values can include additional information, currently Ti2 is expected to run on node version 12.22.8; we suggest you use the same for your codebase.
 
 
 After initializing your git environment for development; you can initialize your node project; we recommend naming your repo ti2-\<pluginname\> but it is not required.
@@ -61,7 +65,7 @@ class Plugin {
 module.exports = Plugin;
 ```
 
-The constructor of the plugins should extend the attributes with the received params, this allows the plugin to receive configurations or settings that are to be used by any user; that is settings that are shared across accounts.
+The constructor of the plugins should extend the attributes with the received params, this allows the plugin to receive configurations or settings that are to be used by any user, for example, settings data that can be shared across accounts.
 
 By default Ti2 will pass down all environment variables that match the plugin name to it's constructor; for example, if the following environment variables are defined:
 
@@ -98,7 +102,7 @@ class Plugin {
 module.exports = Plugin;
 ```
 
-The token parameter includes all the settings for the current configured user; on these example we are defauring this settings to the ones configured to the pluging when it was instanced; so if the user settings do not include an apiUrl it will fall back to the environment variable on the running server.
+The token parameter should store all the settings for the current configured end user; on these example we are defaulting this settings to the ones configured to the pluging when it was instanced; so if the user settings do not include an apiUrl it will fall back to the environment variable on the running server.
 
 ## Testing Suite
 
@@ -141,7 +145,9 @@ describe('Base Tests', () => {
 $ npx jest
 ```
 
-## Adding the folder to a ti2 instance
+## Deploying
+
+### To your own Instance
 
 After setting up a [Ti2 instance]{@tutorial setup-your-instance} you can add your development folder as a package on your instance's npm repo (not on the plugin's instance), like so:
 
@@ -151,13 +157,17 @@ After setting up a [Ti2 instance]{@tutorial setup-your-instance} you can add you
     }
 ```
 
+### To our hosted instance
+
+[Contact us](https://www.ti2.travel/contact-us) with the npm published package to begin the testing and deployment process.
+
 ## Extending the base API
 
-Ti2 uses the [Swagger API specification](https://swagger.io/specification/) standard to define it's own methods, you can review the base methods [here](https://ti2-staging.tourconnect.com/api-docs/); these methods can be extender using the same format; this allows any plugin to extend the base API endpoints that are linked to any plugin method (part of the base methods or new ones).
+Ti2 uses the [Swagger API specification](https://swagger.io/specification/) standard to define it's own methods, you can review the basic methods [here](https://ti2-staging.tourconnect.com/api-docs/); these methods can be extended using the same format; this allows any plugin to extend the base API endpoints that are linked to any plugin method (part of the basic methods or new ones).
 
 All the extender methods would be availble under the /\[plugin name] namespace, i.e.: /ti2-greatPlugin/ping.
 
-For Ti2 to pickup the extender definition one must create a new file on the root of the plugin named api.yml, such file would contain only the methods to be extender and it must comply with the current swagger version used on ti2.
+For Ti2 to pickup the extender definition, one must create a new file on the root of the plugin named api.yml, such file would contain only the methods to be extended and it must comply with the current swagger version used on ti2.
 
 ```yaml
 # api.yml
@@ -202,18 +212,21 @@ paths:
 
 ## Database Migrations (plugin's own database tables)
 
-Ti2 uses [Sequelize v6.13](https://sequelize.org/v6) and is the database ORM we ecourage to use, you can add your own tables via migrations that should be placed under a migrations folder on the root of the plugin folder.
+Ti2 uses [Sequelize v6.13](https://sequelize.org/v6) which is the database ORM we ecourage you to use, you can add your own tables via migrations that should be placed under a migrations folder on the root of the plugin folder.
 
 Migrations should be run after the fact, from the root of ti2 instance like so:
 
-
 ```
-$  npm explore ti2<pluginName> -- npx sequelize db:migrate"
+$ ti2 dbapp [plugin name] migrate
 ```
 
-We strongly encourage all the plugin's table names are predicated with the plugin name (i.e. ti2-pluginName-cacheTable).
+We strongly encourage all the plugin's table names are prefixed with the plugin name (i.e. ti2-pluginName-cacheTable).
+
+This should be executed after all ti2 host migrations had been executed.
 
-This should be executed ater the ti2 project migrations have been executed.
+```
+$ ti2 db migrate
+```
 
 ## Scheduled Task (to be released on v2)
 

package/tutorials/setup-your-instance.md

@@ -1,15 +1,24 @@
-## Initializing your new Repo
+## Why would I want to run my own instance?
 
-We suggest creating a folder with your instance name+i2 (i.e acme-ti2); then initialize an node's npm package and install ti2 along with any plugins to be used.
+* Scenario 1: You want to test your plugins before submitting it to our Ti2 instance, it is a good idea to spin up your own Ti2 test instance, you can test against all the Ti2 REST Apis (In the future, we will provide a Ti2 sandbox instance).
 
-```bash
-$ mkdir acme-ti2
-$ cd acmme-ti2
-$ npm init .
-$ npm i ti2 ti2-tourconnect
-```
+* Scenario 2: You want to host your own Ti2 server so you can have everything under your own control.
+
+When you are runnning a Ti2 server you can access the documentation page on the url (http://[yourinstance]/api-docs/) that shows the available API methods, you can review the [swagger documentation page online](https://ti2-staging.tourconnect.com/api-docs/) .
+
+## Security
+
+An admin api key is set trough an environment variable called adminKey; using this API key is possible to create Users and/or application authentications.
+
+A new User/User Authentication can be created using the endpoint [createUserToken](https://ti2.tourconnect.dev/api-docs/#/admin/createUserToken); the return value consists of a JWT token for further user intraction with the App; the admin API key is required; no password is saved on the server side.
+
+Apps/Integrations can be created using the admin API Key; this after the plugin had been added to the codebase; the app can be created using the endpoint [createApp](https://ti2.tourconnect.dev/api-docs/#/admin/createApp); such endpoint returns a key that can be used by the app to interact with user Ids; such interactions allow the app to push for changes related to user integrations, the app can list the users currently configured for it using the endpoint [listAppTokens](https://ti2.tourconnect.dev/api-docs/#/app/listAppTokens); the passwords for Apps are encripted onde the database using aes-256-cbc, more details can be found on the [``models/integrations.js``](https://github.com/ti2travel/ti2/blob/main/models/integration.js) file.
+
+User + app integration credentials can be added after the app has been added to the system; these can be added by either the user, admin or the app itself using the endpoint [createAppToken](https://ti2.tourconnect.dev/api-docs/#/app/createAppToken). These keys are saved in JWT format on the database.
 
-## Requirements
+## Get Started
+
+### Requirements and Evironment variables
 
 A MySQl instance is required and the following environment variables are required:
 
@@ -28,13 +37,25 @@ frontendKey=IpOiLahrGQxsQimwoK7Z
 adminKey=bCviyz7iKyuEBoOVlODn
 ```
 
-After installing the ti2 package you need to run the datbase migrations for ti2:
+### Initialize a new NodeJS project
+
+We suggest creating a folder with your instance name+i2 (i.e acme-ti2); then initialize an node's npm package and install ti2 along with any plugins to be used.
+
+```bash
+$ mkdir acme-ti2
+$ cd acmme-ti2
+$ npm init .
+$ npm i ti2 ti2-tourconnect
+```
+
+
+After installing the ti2 package you need to run the database migrations for ti2:
 
 ```
-$  npm explore ti2<pluginName> -- npx sequelize db:migrate"
+$  ti2 db migrate
 ```
 
-## Entry File
+### Entry File
 
 then just create an entry file like this :