cs.punk Posted May 24, 2012 Share Posted May 24, 2012 Hey guys. I have a site that has a bit of an audience now days, so usually when I've done some work on it, to 'update it' I'd just open filezilla, delete all files on the live server, reupload the new ones and fix any thing I've forget to change (database credentials etc). Although obviously it's not the most effective way to do it. Can anybody share how you go about it? Quote Link to comment Share on other sites More sharing options...
kicken Posted May 24, 2012 Share Posted May 24, 2012 I generally keep my sites in a SVN repository and will commit changes as I finish them. When it's time to update I just do a 'svn update' command on the server to download all the latest files. All the database/email/etc settings that vary based on environment are inside a config.inc.php file which is on the svn ignore list and not part of the repository (there is a template w/o any real values in the repository as config.inc.php.base). The updates are usually pretty quick as it only updates whatever has changed rather than having to upload every file. Changes to the config file are rare and just handled manually. Database changes I do manually prior to the file updates. Quote Link to comment Share on other sites More sharing options...
trq Posted May 24, 2012 Share Posted May 24, 2012 Like kicken I keep my work under version control (Git). Once a release is tagged complete though, I usually use rsync to upload the new site. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.