You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I must admit this volume plugin is exactly what I've been looking for. I currently run a bunch of apps where I use git as a means of config version control and a bash script does a push/pull to load new config and reload the daemon.
I was wondering how this volume behaves when the container attached to it is recreated, does it pull the content again? So if container 1 is created using the volume, then the git repo is updated and container 2 is created, will container 2 see same files as container 1 or it would see the new updated content?
How hard would it be to modify this plugin to allow it to push updated files as commits back to the repo? This could happen upon removal of the volume or at intervals.
Is it possible to periodically check if there are new commits in the repo, pull them and restart the containers that are attached to the volume (to enforce them to load the new config).
Doing this in the volume plugin would be awesome, otherwise I will probably deploy my update script into the images or use bind mounts for now.
Thanks!
The text was updated successfully, but these errors were encountered:
Hey
I must admit this volume plugin is exactly what I've been looking for. I currently run a bunch of apps where I use git as a means of config version control and a bash script does a push/pull to load new config and reload the daemon.
I was wondering how this volume behaves when the container attached to it is recreated, does it pull the content again? So if container 1 is created using the volume, then the git repo is updated and container 2 is created, will container 2 see same files as container 1 or it would see the new updated content?
How hard would it be to modify this plugin to allow it to push updated files as commits back to the repo? This could happen upon removal of the volume or at intervals.
Is it possible to periodically check if there are new commits in the repo, pull them and restart the containers that are attached to the volume (to enforce them to load the new config).
Doing this in the volume plugin would be awesome, otherwise I will probably deploy my update script into the images or use bind mounts for now.
Thanks!
The text was updated successfully, but these errors were encountered: