i have application structure.
/path/releases
/path/releases/01012016
/path/releases/16012016
/path/releases/etc..
and
/path/dev
(symlink version)/path/stag
(symlink version)/path/stable
(symlink version)
my docker-compose.yml looks this:
nginx: ... volumes_from: - data php: ... volumes_from: - data data: volumes: - /path/stable:/var/www
i known docker resolves symlinks. have thought before deploy recreate data container , it's ok. it's not.
i have recreate containers taking volumes data container.
any idea how make better, mean better automatic? remove symlinks , put last version docker-compose
? mark parent folder volume , resolve via relative symlink? or other solution.
which solution best you. what's best practice.
thank you. felix
if want make more automatic, recreating containers in 1 docker-compose.yml can achieved docker-compose --force-recreate
.
another solution be:
/path:/var
…then ln -s /path/releases/06012016 /path/www
when want change.
i don't solution exposes releases inside containers. rather go full restart --force-recreate.
Comments
Post a Comment