title: Best practice updating a website
body: <p>currently my work-flow is as follows:</p>
  
  <p>Locally on a machine I maintain a git repo on each website I am working on, when the time comes to publish something I compress the folder and upload this single file to the production server via ssh then I decompress, test the changes a move the changes to the live folder and I get rid of the .git folder.</p>
  
  <p>I was wondering if the use of a git repo on the live server was a good idea, seems to be at first but it can be problematic if a change doesn't look the same on on the production server in comparison to the local development machine... this could start a fire...
  What about creating a bare repo on some folder on production server then clone from there to the public folder thus pushing updates from local machine to the bare repo and pulling from the bare on the public folder of the production server... may anyone plese provide some feedback.</p>
  
  <p>Later I read about capistrano <a href="http://capify.org" rel="nofollow noreferrer">http://capify.org</a> but I have no experience w/ this software...</p>
  
  <p>In your experience what is the best practice/methodology to accomplish a website deployment/updates?</p>
  
  <p>Thanks in advance and for your feedback.</p>