Continuous Code to Container Delivery

cwingrav commented 5 years ago

I've been beating around the edges with 'vh' and pods in cluster. It would be fairly trivial to automate sending of files to a running stage as the user develops. It wouldn't be interactive (though you could log into container as well), but with nodemon instead of node, it would sync locally saved changes to the container in the cluster. Like nodemon locally. Nodemon in container would then restart the container.

Would it read in env changes?
would it know what to monitor?
build this into the container's recipe too?
if container restarts, then mirror changes to running cluster again
on start, pushes local changes... read in from git?
would it need to tag containers with a version so it knows which git to compare against?

ex. wov-mirror CONTAINER <- and it runs continuously until killed...

cwingrav commented 5 years ago

https://askubuntu.com/questions/339230/how-do-i-trigger-rsync-on-file-modification

https://linux.die.net/man/1/inotifywait

Looks like you could easily get this by: 1) build a container using nodemon instead of node 2) change recipes so they write a file to copy in src and a list of files/directories to monitor 3) use https://linux.die.net/man/1/inotifywait to monitor from the monitor files/dirs and then run the rsync/copy recipe, the use kubernetes copy... nodemon will kick in at that point

cwingrav commented 5 years ago

Similar to https://tilt.dev

woveon / wovtools

Continuous Code to Container Delivery #44