Comment by j on "How to handle multi microservice deployment from a single GitHub project?"

I've done this with fabric and rsync.

a yml file where machines are defined and all roles are defined a deploy user on all machines

packages were built on the deployment server. a new timestamp version was written in the "version_file"

rsync runs and copies all file. the symlink on the host systems gets changed to the new version and if something fails you can always go back one version based on the file name.

took me two weeks to write it that way but still it was fabric (python) and not capistrano (ruby)

and I actually used the linux kernel for the whole syncing and so on so the OPs guys could debug and easily trace those things in their domain.

hey @chilimatic, what's the nicest way to find out whether or not a file has changed after doing a git pull (preferably using a shell script)?

@spsiddarthan inotify would be one possibility :) and I used this 5 years ago http://iwatch.sourceforge.net/index.html don't know if it scales on your need

maybe https://github.com/c4milo/node-inotify since you guys work with node :)

Thanks @chilimatic, I will try the later one out. :)

@spsiddarthan let me know what you've picked, or if you picked something else :D it's always good to learn new things :D

Thanks, will check it out. I was looking to see if there was an out-of-box solution with capistrano.

@keenavasan np :) i just wanted to give an answer that could be useful :) if you stick to your stack that's obviously the better choice :)

Search Hashnode