Why use a Rails-like deployment mechanism over 'git pull' for releasing?
        Posted  
        
            by Chad Johnson
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by Chad Johnson
        
        
        
        Published on 2010-04-20T23:14:50Z
        Indexed on 
            2010/04/20
            23:33 UTC
        
        
        Read the original article
        Hit count: 303
        
To release my centralized webapp, I COULD have a vhost pointed to some directory and then just do a 'git pull' when I want to release, updating the files. But Rails has a different deployment mechanism: it copies files to a subdirectory and then points a symlink ('current') to that new subdirectory.
I understand that it probably more acceptable to do a Rails-like deployment because the release is built in some directory, and then the symlink is pointed to that directory, so this is much faster, and it's less likely that users would experience weird issues while a release is happening.
Are there any other advantages to the Rails approach? Or, is a 'git pull' approach actually more widely accepted?
© Stack Overflow or respective owner