pyBanca Infrastructure

Infraestructure behind the app.

STACK (wip)

• Elmlang for the frontend. Runing at port 80.
• Japronto for the WSGI/API service. Runing at port 8080 proxy-served by port 8000.
• SQLAlchemy as ORM.
• MariaDB as RDBMS. Runing at port 8336.

CI

• Jenkins (EDIT: will have his own container)
• Travis (more research needed)

Deployment (pipeline perhaps)

• We will have a Docker container with Alpine runing our WSGI python backend.
• The backend will serve an index.html that calls an index.js where our Elm app lives.
• First, give the webpack order to compile the elm files and prepare them for production.
• And later, do the thing.

Environment

• Alpine docker container (with gcc libs)
• python 3.6.3 && 2.7.14: needed for webpack 3 plugnins (updating to webpack 4 will solve this)
• nodejs v8.9.3
• webpack 3.10.0
• elm 0.18
• mariadb

Dev dependencies

• Linux :^)
• Docker
• Some visual database modeler, like MySQL Workbench.
• A text editor: VS Code, Vim, Sublime or Atom. (yes, ordered by likeness).
• A terminal (with zsh perhaps?)
• Good intentions :)

TODO

• Config files (thinking in the 12 factor apps).
• Chosing IaaS: heroku or google.
  • Hint: we cab user heroku as our staging and google compute engine as production.
• Do a stress test: lets see if that of 1.2 millons of request are true.
• Update Webpack to 4.
• Facture the stack in microservices.
• Research about python watcher.

Q/A

• Q: Why ignore the package-lock.json?
  • this introduces more conflicts and problems than resolve (ref).
• How to update/deploy a new image?
  • $ docker commit ${CONTAINER_NAME} ${USER}/${DESIRED_IMAGE_NAME}:${DESIRED_TAG}
  • $ docker push ${USER}/${DESIRED_IMAGE_NAME}:${DESIRED_TAG}
  • update the init.sh.