Skip to content

Latest commit

 

History

History
68 lines (52 loc) · 2.42 KB

external_db.rst

File metadata and controls

68 lines (52 loc) · 2.42 KB

Using external Database

Services

  • server
  • reports
  • scheduler
  • analytics_front
  • data
  • audit

You should spin up a mongodb externally, you can do using the MAESTRO_MONGO_URI env variable.

Env Variables

Default

Description

MAESTRO_MONGO_URI

mongodb://localhost:27017

Can be mongodb or mongo+srv://

services:
server:
    image: maestroserver/server-maestro
    environment:
    - "MAESTRO_MONGO_URI=mongodb://{external.mongo.url}"
    - "MAESTRO_MONGO_DATABASE=maestro-client"

reports:
    image: maestroserver/reports-maestro
    environment:
    - "MAESTRO_MONGO_URI=mongodb://{external.mongo.url}"
    - "MAESTRO_MONGO_DATABASE=maestro-reports"

scheduler:
    image: maestroserver/scheduler-maestro
    environment:
    - "MAESTRO_MONGO_URI=mongodb://{external.mongo.url}"
    - "MAESTRO_MONGO_DATABASE=maestro-scheduler"

analytics_front:
    image: maestroserver/analytics-front-maestro
    environment:
    - "MAESTRO_MONGO_URI=mongodb://{external.mongo.url}"
    - "MAESTRO_MONGO_DATABASE=maestro-client" # <------ It need to be the same db of server-api

data:
    image: maestroserver/data-maestro
    environment:
    - "MAESTRO_MONGO_URI=mongodb://{external.mongo.url}"
    - "MAESTRO_MONGO_DATABASE=maestro-client" # <------ It need to be the same db of server-api

audit:
    image: maestroserver/audit-app-maestro
    environment:
    - "MAESTRO_MONGO_URI=mongodb://{external.mongo.url}"
    - "MAESTRO_MONGO_DATABASE=maestro-audit"

You can replace the db name using the MAESTRO_MONGO_DATABASE env var.

Env Variables

Default

Description

MAESTRO_MONGO_DATABASE

maestro-client

Database name