-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
Watchers as daemons ? #51
Comments
Well could you clarify how you run you stack, are you using
right? Because when using In general, i like the daemons idea, which also kinda does not block your cli anymore. I am not sure how easy it is since we already run 2 threads, which need to be handled then. Do you have any experience with this kind of implementation in ruby? |
We could also easy implement this in a separate gem and use docker-sync as a library https://github.com/EugenMayer/docker-sync/wiki/7.-Scripting-with-docker-sync I do something similar, since after the sync stack starts, i want not only the compose stack to start up, when its started, i want to pre-deploy a developer instance in my drupal. To orchestrate all this, i use a own thor script, docker-sync and docker-compose as libraries
This would starts docker-sync, then a a PHP7 driven stack for drupal ( compared to the default php5.5 stack ) implemented by overlays with docker-compose-gem, then it pre-installs an instance ( well this is done using consul mainly, but that does not really matter here ). What i want to say, docker-sync can be used as a lib, also as a lib for a daemon. The question is, if we want the daemon to be an extra-thing without adjusting docker-sync but rather use it as a lib, or if we want to internally change the way docker-sync runs. We might need to both, anyways |
👍 for wrapping whole thing into Daemons and adding option ( I for example don't use |
Since for now, the only hurdle to have your use case covered already @midN , is starting a new console cli, i will not actively work on this. I am concentrating on keeping things stable and smooth right now and would be happy if contributors would add features they need for their use case. Hope that makes sense You can use a console to start
And use a different console to do
Be aware of the scripting options though https://github.com/EugenMayer/docker-sync/wiki/7.-Scripting-with-docker-sync .. you can implement docker-sync as a library and as we do, implement you special docker-compose logic very convenient. |
merged in 0.2.0 |
Hi,
I would love to have the opportunity to start / stop watchers from external calls. This would allow deactivating syncing temporarily when performing some tasks and reenable when needed.
The first use case of this is currently while installing Drupal from composer, we could wait the end of the bootstrapping script and the run manually a sync task.
What do you think of that ? what about implementing them as daemons ?
The text was updated successfully, but these errors were encountered: