Protect file system from mid-deploy failures

[beck]

@stefanor has plans for this:

stage all templating into a directory tree inside the deployed app. And then just copy the whole directory tree to /etc/ when deployed

[beck]

Question, why not:

Keep the templating stage inside the app dir, symlink vhosts and includes (or any other filesystem updates) to said templating stage via the deployed dir's live symlink. That way all file system updates happen with a single swing.

[thomasw]

What @stefanor described was actually how I thought it worked now.

[stefanor]

@beck: That is probably even better, yes. But it won't work for everything. Upstart monitors job file changes with inotify, and won't detect the symlink swap. Other things may, too.

[beck]

won't detect the symlink swap

When a symlink is touched do the monitors fire? If yes, then content changes could happen with a single swing followed by a touch of all incoming symlinks.

This may be a bit of an over-engineered solution for our needs, I think your approach would be good enough. I'm just experiencing some PTSD when I had to use WordPress and deploying an update made everything explode.

[stefanor]

No, upstart explicitly ignores symbolic links.