jcao02 / lafabrika-backoffice-backend

Backend services to hold backoffice operation within the company

La Fábrika Backoffice Backend

Backend services to hold backoffice operation within the company.

Services

• Accountability: Handles the company's accountability.
• Database: Persists the data used by the services.
• Migrations: System to make migrations in the database service.
• Authentication: Handles the user authentication

Containers

The app is contained in Docker. Each service has its own Dockerfile and they're composed using the docker-compose.yml in the root folder.

Versions:

1. docker: >=18.09.3
2. docker-compose: >=1.23.2

To start developing:

1. Go to services/database and run docker build . -t lafabrika/database:0.0.1
2. Run npm install in each service and model that contains a package.json
3. Go to the root folder and run docker-compose up

lafabrika-backoffice-backend's Issues

Development scripts

• Mount script
• Start script
• Migrate script (Will do it if necessary in the future)

Create users database

This includes only the migration to add the proper tables and constraints to hold users in the DB

• Schema lafabrika
• users table
• Database path to lafabrika schema
• Update migrations README.md

Grant all privileges to role lafabrika on schema lafabrika

That way lafabrika role will be able to modify/use tables, sequences, etc

Setup Travis CI

Connect services to internal network

Only if they need to connect to the database or or another service

• Authentication
• Users
• Accountability

Dockerize development environment

• Create base image.
• Create Node image.
• Create PostgreSQL image.
• Create sqitch image.
• Create app image.
• Create docker-compose with app, db and migration services.
• Update README.md

Development environment

Stack:

• HapiJS (Routing)
• Objection (ORM)
• PostgreSQL
• Sqitch (Migrations)

To-do:

• Docker Image: Base (ubuntu + basic software).
• Docker Image: NodeJS.
• Docker Image: Sqitch.
• Docker Image: accountability service.
• Docker Image: users service.
• Docker Image: authentication service.
• Docker Image: PostgreSQL.
• Docker compose to mount server
• Mount script
• Start script

Configure ENV variables in authentication service

Specifically:

• PG_CONNECTION_URI
• JWT_PRIV_KEY

Both seems to be perhaps shared variables among the different services

Ensure casing in email uniqueness

[email protected] should be equal to [email protected]

U.S: As an anoymous user, I can sign-in to use the system.

• DB
• ORM
• Route
• Handler

Separate user private information from public information in Database

We currently have a table users which contains a password column. We need to add a new table called ùsers_private with the password column and remove the password column from the users.

This way the private information needs to be fetch explicitly making a join in both tables.

TODO:

• Separate tables
• Update check_user_password_combination function
• Add function insert_user_with_password

Add users service

This includes only the service setup

User Stories

Authentication

• As an anoymous user, I can sign-in to use the system.

Users

• As an admin user, I can register non-admin users to manage the system.
• As an admin user, I can delete non-admin users to remove them from the system.
• As a user, I can change my password to set a new one.
• As an admin user, I can reset a non-admin user password in case they forgot it.
• As an admin user, I can list all the users in the system.

Add authentication service

This only includes the service setup (basic server, docker configuration and composing)