Current setup:
Running gdev up starts data container and automatically syncs initial state.
Then it starts other containers which can mount files from data container.
Then it starts unison file watcher to sync files as they change to and from data container.
Preferred way:
Stop automatic sync watcher in the end of gdev up and provide another command which can be used as file sync watcher for project.
gdev up should tell the user to run gdev sync if onnimonni/unison container is available in docker-compose.yml.
It should check if docker-compose is running and fail with sane error message if it isn't.
Current setup: Running
gdev up
starts data container and automatically syncs initial state. Then it starts other containers which can mount files fromdata
container. Then it starts unison file watcher to sync files as they change to and fromdata
container.Preferred way: Stop automatic sync watcher in the end of
gdev up
and provide another command which can be used as file sync watcher for project.gdev up
should tell the user to rungdev sync
ifonnimonni/unison
container is available indocker-compose.yml
.It should check if docker-compose is running and fail with sane error message if it isn't.