Files
hasura-backend-plus/docker-compose.development.yaml
Pilou 29b4d913d4 Clean docker and migrate (#189)
* feat: autoload migrations and simplify start script

no need to get the migrations from the migration files from the repo and to mount a specific volume
to the Hasura GE service. By default, when HBP starts, it checks the migrations and installs it if
required. This can be disabled by setting AUTO_MIGRATE to false. This system could be extended to
set AUTO_MIGRATE=v1 so it runs another set of migrations that would transform schema and data from
HBP v1 to HBP v2

* fix: include mock migrations used for testing

* fix: run migrations in a separate node script

* refactor: better general repo structure, and migration that works

* ci: change test mock migration folder in GH actions
2020-04-30 15:10:12 +02:00

33 lines
785 B
YAML

version: '3.6'
services:
hasura-backend-plus:
build:
context: .
dockerfile: Dockerfile.dev
env_file: '.env.development'
depends_on:
- 'mailhog'
environment:
NODE_ENV: development
JWT_ALGORITHM: HS256
JWT_KEY: '${JWT_KEY}'
SMTP_HOST: mailhog
SMTP_PORT: 1025
SMTP_SECURE: 'false'
volumes:
- .:/app
- /app/node_modules
graphql-engine:
ports:
- '8080:8080'
environment:
HASURA_GRAPHQL_JWT_SECRET: '{"type": "HS256", "key": "${JWT_KEY}"}'
minio:
ports:
- 8000:9000 # Do not use port 9000 in the host machine as developpers using portainer might already use it
mailhog:
image: mailhog/mailhog
ports:
- 1025:1025 # smtp server
- 8025:8025 # web ui