02-16-2010, 04:56 PM
|
#3 (permalink)
|
|
The Visitor
Join Date: Feb 2010
Location: Juno Beach, FL
Posts: 2
Thanks: 0
|
A method that I prefer is to use subversion. Not only because it keeps revision of previous edits to the system, but because it is very simple to run only one line of code to update the server. Typically I work on my tree, then when it is ready I just do a svn update to my path on the tree and it is updated instantly. The nice thing is, it saves bandwidth, depending on your system size; you are only updating the changes to the files instead of overwriting each file. Then in a worst-case-scenario, you would have the power to revert to an older revision, if a serious bug arises. This is a method I have gotten spoiled with and encourage others to use. I develop on my localhost and when I am ready I commit the files to the tree, when I am finished with a part of the system I will then update the server for the changes to take effect.
There are plenty of free svn repos out there. Sourceforge, google code, and my favorite and the one I am currently using, is beanstalkapp.com. No matter your system, svn can be installed. Client and server side (haven't found a system yet that it can't be installed on). If your server does not have svn installed it may be difficult for some to install it.
rsync is useful but I have only used it for cloning hard-drives, in-fact I never knew you could use it this way. Very intriguing.
I would like to make a side-note. Git is suppose to be better than subversion but I have not been able to take that challenge. I have used CSV and SVN for years and, like a Tivo, I don't know how I would survive without it.
My two cents.
|
|
|
|