-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add compose file #10
Comments
Problem are one time commands like the |
After some experimentation I realized that this is not as easily done as I hoped. Problems are:
To fix those issues the docker images have to be changed to not rely on those linked env variables. Also the initialization steps can be incorporated in a custom command script that checks whether initialization has already been done (and skips it in this case) and then runs the current command. This way the command does the initialization if required but remains idempotent. The same applies for the provisioning container ( Despite those issues I managed to get things running with
Content of version: '3'
services:
chado_db:
image: postgres:9.6
environment:
POSTGRES_USER: tbro
POSTGRES_PASSWORD: tbro
POSTGRES_DB: chado
worker_db:
image: postgres:9.6
environment:
POSTGRES_USER: worker
POSTGRES_PASSWORD: worker
POSTGRES_DB: worker
worker_ftp:
image: tbroteam/tbro_worker_ftp
environment:
FTP_USER: tbro
FTP_PW: worker
worker:
image: tbroteam/tbro_worker
links:
- "worker_db:WORKER"
environment:
WORKER_ENV_DB_NAME: worker
WORKER_ENV_DB_USER: worker
WORKER_ENV_DB_PW: worker
WORKER_PORT_5432_TCP_PORT: 5432
tbro:
image: tbroteam/tbro_apache
ports:
- "80:80"
depends_on:
- chado_db
links:
- "worker_db:WORKER"
- "chado_db:CHADO"
environment:
WORKER_ENV_DB_NAME: worker
WORKER_ENV_DB_USER: worker
WORKER_ENV_DB_PW: worker
WORKER_PORT_5432_TCP_PORT: 5432
WORKER_PORT_5432_TCP_ADDR: WORKER
CHADO_ENV_DB_NAME: chado
CHADO_ENV_DB_USER: tbro
CHADO_ENV_DB_PW: tbro
CHADO_PORT_5432_TCP_PORT: 5432
CHADO_PORT_5432_TCP_ADDR: CHADO |
No description provided.
The text was updated successfully, but these errors were encountered: