edombowsky/work-order-storage

The Work Order Storage service is responsible for persisting into PostgreSQL, entities that reside within the Work Order domain (i.e. work orders, work order templates, and work order dependencies). The Work Order Storage service is also responsible for servicing requests for data from the Work Order domain (e.g. from API services).

Introduction

The Work Order Storage service is responsible for persisting into PostgreSQL, entities that reside within the Work Order domain (i.e. work orders, work order templates, and work order dependencies). The Work Order Storage service is also responsible for servicing requests for data from the Work Order domain (e.g. from API services).

Install a PostgreSQL docker container.

See detailed instructions here.

• Creates a database named postgres with username postgres and password docker.
• Data will be persisted in $HOME/docker/volumes/postgres

mkdir -p $HOME/docker/volumes/postgres
docker run --rm --name pg -e POSTGRES_PASSWORD=docker -e POSTGRES_USER=postgres -e POSTGRES_DB=postgres -d -p 5432:5432 -v $HOME/docker/volumes/postgres:/var/lib/postgresql/data postgres

• Run the migration

sbt flywayMigrate

References

• HikariCP
• CRUD Repositories for Slick based persistence Scala projects
• Slick Extensions for PostgreSQL
• Handling Postgres json datatype in slick, scala
• Flyway
• Flyway Migration Javadoc
• Simple Slick example
• Postgres.app
• Creating user, database and adding access on PostgreSQL
• How to Change a User to Superuser in PostgreSQL
• PostGis for Postgres on MacOS
• Some time utilities