Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • V VesselAI - Harmonization
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VesselAI
  • VesselAI - Harmonization
  • Issues
  • #2

Closed
Open
Created Mar 18, 2022 by Ricardo Grim Cabrita@grimMaintainer

App should bootstrap its own databases

Currently database bootstrapping is done via both Mongo's and Postgres' initdb scripts.

docker
├── mongo
│   └── initdb.d
│       └── mongo-init.js // <--
└── postgres
    ├── ais_data_backup.sql // <--
    ├── boost_rs_backup.sql
    └── create_tables.sql
  mongo:
(...)
    volumes:
      - ./mongo/initdb.d/mongo-init.js:/docker-entrypoint-initdb.d/mongo-init.js
  postgres:
(...)
    volumes:
      - ./postgres/ais_data_backup.sql:/docker-entrypoint-initdb.d/ais_data_backup.sql

Ideally the user shouldn't have to handle this and the app should do the bootstrapping on its own, when presented with an empty database.

Assignee
Assign to
Time tracking