Version Control, and more
#1
Posted 11 January 2008 - 02:31 PM
There was a lot of chat about getting some sort of version control software up and running a while back - did anything come of that? The reason I'm asking is that I'm now very interested in using Subversion for a current project as managing code between three individuals without it can beb potentially quite frustrating.
I'm also wondering if it will be possible to scrub my old wiki and set up a new one, as well as Mantis for bug tracking?
Thanks!
AmberZ
#2
Posted 11 January 2008 - 04:11 PM
Here's a sample of it working:
http://svn.ppmsite.com
Command & Conquer Mods, Mods Support, Public Researchs, Map Archives, Tutorials, Tools, A Friendly Community and much more. Check it out now!
#3
Posted 11 January 2008 - 07:45 PM
#4
Posted 13 January 2008 - 12:40 AM
Command & Conquer Mods, Mods Support, Public Researchs, Map Archives, Tutorials, Tools, A Friendly Community and much more. Check it out now!
#5
Posted 13 January 2008 - 09:40 PM
~jnengland77
#6
Posted 14 January 2008 - 10:47 AM
#7
Posted 14 January 2008 - 12:37 PM
World Domination Status: ▾2.7%
#8
Posted 21 January 2008 - 06:33 PM
~jnengland77
#9
Posted 21 January 2008 - 09:55 PM
We're sheelabs (gamemod.net), and any reasonable address is fine. We'd like it shared, as that's the most useful way of organising it, and a websvn front end would be nice but isn't necessary. Additional users would accumulate over time, as the team changes, so if I'm unable to add users myself I'll have to keep bugging - I'll PM a set of user names to cover the current core later if you wish, but for now you can just include myself. Let me know if you need anything else.
We'll also need a fresh MySQL database for a new wiki - if you can scrub the old one that's fine, but replacing it is also fine, I can just delete and reinstall media wiki
#10
Posted 22 January 2008 - 03:23 AM
Good luck,
jnengland77
#11
Posted 22 January 2008 - 08:35 AM
#12
Posted 25 January 2008 - 09:20 AM
Also, committing to SVN seems to be painfully slow, what are the upload speeds like? It might better help me work out what sort of chunks I should be committing at any given time.
#13
Posted 25 January 2008 - 09:22 PM
Command & Conquer Mods, Mods Support, Public Researchs, Map Archives, Tutorials, Tools, A Friendly Community and much more. Check it out now!
#15
Posted 26 January 2008 - 05:13 PM
#16
Posted 26 January 2008 - 10:05 PM
Command & Conquer Mods, Mods Support, Public Researchs, Map Archives, Tutorials, Tools, A Friendly Community and much more. Check it out now!
#17
Posted 27 January 2008 - 02:51 PM
Some of our binary files could potentially get around 100mb+.
#18
Posted 05 February 2008 - 09:16 AM
#19
Posted 06 February 2008 - 03:35 AM
World Domination Status: ▾2.7%
#20
Posted 25 March 2008 - 11:27 AM
Be patient with large files
A nice feature of Subversion is that by design, there is no limit to the size of files it can handle. Files are sent "streamily" in both directions between Subversion client and server, using a small, constant amount of memory on each side of the network.
Of course, there are a number of practical issues to consider. While there's no need to worry about files in the kilobyte-sized range (e.g. typical source-code files), committing larger files can take a tremendous amount of both time and space (e.g. files that are dozens or hundreds of megabytes large.)
To begin with, remember that your Subversion working copy stores pristine copies of all version-controlled files in the .svn/text-base/ area. This means that your working copy takes up at least twice as much disk space as the original dataset. Beyond that, the Subversion client follows a (currently unadjustable) algorithm for committing files:
* Copies the file to .svn/tmp/ (can take a while, and temporarily uses extra disk space))
* Performs a binary diff between the tmpfile and the pristine copy, or between the tmpfile and an empty-file if newly added. (can take a very long time to compute, even though only a small amount of data might ultimately be sent over the network)
* Sends the diff to the server, then moves the tmpfile into .svn/text-base/
So while there's no theoretical limit to the size of your files, you'll need to be aware that very large files may require quite a bit of patient waiting while your client chugs away. You can rest assured, however, that unlike CVS, your large files won't incapacitate the server or affect other users.
Einstein: "We can’t solve problems by using the same kind of thinking we used when we created them."
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users