Skip to content

Set up CAPO for new middle layer

Sam Kagan requested to merge setup-capo into spike-branch-removing-postgREST

Right now, CAPO just manages db connection strings and repo types

CAPO supports only non-Docker, in-memory repo and Dockerized, Postgres repo, in local.properties and dsoc-dev.properties, respectively. Specifically, the following additions must be made to these two CAPO profiles:

local.properties

# For TTAT's local non-Docker deployment
ttat.repository.type = inmemory

dsoc-dev.properties

# For TTAT's local Docker-compose deployment
ttat.repository.type = sqlalchemy

ttat.repository.db.driver   = org.postgresql.Driver
ttat.repository.db.protocol = postgresql://
ttat.repository.db.url      = db:5432/archive
ttat.repository.db.username = archive
ttat.repository.db.password = docker

This branch introduces no opinions about CAPO_PATH, it must be set locally.

Edited by Sam Kagan

Merge request reports