Intro

Node JS / Express server for the VLife app

Dependencies

MySQL

Issues when dropping tables or schemas

if you get something about the SDI schema, delete all rows in table before dropping it.

Issues when accesing some specific table or view

Sometimes the user can't access a view or a table, directly or by a join, so double check if the user can read that view or table

if it is a view, be careful with this line

/_!50013 DEFINER=root@localhost SQL SECURITY DEFINER _/

this can mess with the access privileges

Typescript

For type safety and OOP.

Types to add

"@types/express": "^4.17.1",

"@types/jest": "^24.0.18",

"@types/mysql2": "github:types/mysql2#semver:^1.0.0",

"@types/supertest": "^2.0.8",

Installing them

• mysql2

  npm i --save-dev types/mysql2#semver:^1.0.0

body-parser

https://github.com/babel/example-node-server

yarn add body-parser

DEV

• for es6 npm i @babel/cli @babel/core @babel/preset-env @babel/node nodemon --dev

• for watching file changes npm i nodemon --dev

• for eslint (ECMAScript syntax validation) npm i eslint eslint-config-standard eslint-plugin-import eslint-plugin-node eslint-plugin-promise eslint-plugin-standard --dev

• for testing npm i mocha @babel/register --dev

preset-es2015 and preset-stage-x are deprecated as of 6-2019

Run locally

$ npm run start

npm scripts

"build": "babel index.js -d dist", // builds locally, transpiles with babel and puts results in /dist

// run build, then serves web app with nodemon (autorefresh) from dist/index.html as entry point
"start": "npm run build && nodemon dist/index.js",

"serve": "npm run build && node dist/index.js", //  run build, then serves web app with node (without autorefresh) from dist/index.html as entry point

"test": "npm run build && mocha --require @babel/register" // run test with mocha framework

$ npm run start

Directory structure

• src
  • routes: API endpoints
  • controllers: logic, provides data to endpoints, mvc pattern
  • models: data models, mvc pattern.
  • schemas, connection to DB
  • types: typescript types

Data modelling

Entities

• Especialidad
• ListaPrecios
• Pago
• Pais
• Practica
• Profesional
• Provincia
• RangoEdad
• Reputacion
• Solicitud
• Usuario

creating sequelize models

sequelize model:create --name Usuario --attributes nombre:string sequelize model:create --name Especialidad sequelize model:create --name ListaPrecios sequelize model:create --name Pago sequelize model:create --name Pais sequelize model:create --name Practica sequelize model:create --name Profesional sequelize model:create --name Provincia ...

Deploy

API - Local Endpoint

localhost:3000/

localhost:3000/usuario

localhost:3000/practica FORBIDDEN? necesita loguearse con JWT

localhost:3000/cantPorEspecialidad FORBIDDEN? necesita loguearse con JWT

AWS

API deployed in EC2 (us-east-1)

connect with SSH

URL: check EC2 instance connect details in AWS Account keys: check Key Pairs item in the NERTWORK & SECURITY section of the EC2 in the AWS Account Remember to update the sec group with your machine IP

check process running

ps x | grep

Heroku - DEPRECATED

install heroku client

https://devcenter.heroku.com/articles/heroku-cli

Commands

• check remotes

  git remote -v

GIT URL: https://git.heroku.com/vlife-api.git

• login into the git account with SSH

  heroku login

• push changes from the heroku-deploy branch to the remote "heroku" master branch

  $ git push heroku master

The remote + branch that has to be updated to trigger a deploy in heroku is the remote "heroku" branch "master" so if you do:

We will organise like this:

In "origin" remote repository, we will have a "master" branch were we put the changes we want to go to heroku, we merge our changes to this branch (origin/master) and then push them to heroku / master

origin / master -> heroku / master

In the master branch

$ git push heroku master

That will push the current master local branch changes to the remote "heroku / master" triggering a new deploy.

check logs

real time log view

heroku logs --tail