|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
|
||||
|
||||
|
I need some basic advice on using Subversion
I'm trying to get everyone using Subversion where I work but am confused on some issues.
We only have Windows machines, so can I install it on a Windows platform? Do we need to set it up as part of a server, e.g. Apache to have network access within our office? We will probably want to export sites to remote servers. What should I do to set it up in the right way? Thanks,
__________________
. How To Ask Questions The Smart Way :: Cheat Sheets :: Flash :: PHP :: MySQL :: 13 Moon Facebook App. :: Compare Game Prices ben.w on del.icio.us"All matter is merely energy condensed to a slow vibration. We are all one consciousness experiencing itself - subjectively. There is no such thing as death, life is only a dream. We are the imaginations of ourselves." - Bill Hicks "Truth is hidden in the subtle nature of the heart of everything, although it is invisible. One cannot see it from inside and neither from the surface. One can only live and experience it." - Heart Sutra |
|
#2
|
|||||
|
|||||
|
Quote:
Yes. Platform is not an issue. Quote:
The subversion server can run in two ways. The first is as a standalone server provided by subversion itself. The second is through apache using a module. Unless you have some server constraints not specific to subversion, it won't matter which method you use. Quote:
Since it seems that you and your colleagues are not subversion users, the hard part is not setting up the server, but more importantly, getting everyone to use it properly. For example, significant code that I work on is setup in trunk, branch, and tag folders. Trunk is the main "stable" code that I ensure always compiles/works. If someone wants a playground for code, they can always use a branch. Seriously, if you can get your developers to consistently checkout and commit their work, rather than checkout and leave it on their machines, you'll have made significant progress. And as mentioned above, getting a stable branch to always compile (i.e. your developers don't commit bad code to the trunk). |
|
#3
|
||||
|
||||
|
Thanks,
I think we have a machine with SUSE Linux on, would it be best to install the Subversion on there (I heard that Windows can be 2x slower)? It seems easier to use svnserve than Apache but I don't understand how to use it. I just installed Subversion onto a remote drive U:\ from my local drive C:\ Is svnserve part of Subversion? I have a SSH client, Putty, so do I have to use that to enter Subversion commands? Hmm I think I can develop in Zend Studio, which might make things easier. I also installed the Tortoise GUI, and if I right-click somewhere I can "Create Repository", is that all I have to do? It sounds too easy to be true! I've been reading the Subversion FAQ and Book but still not getting it as I'm not very good with networking tech speak. Last edited by b3n : September 21st, 2006 at 04:59 AM. |
|
#4
|
||||
|
||||
|
my reply wasn't showing up
|
|
#5
|
|||||
|
|||||
|
Quote:
Subversion runs fine on both linux and windows. There aren't any platform issues you should worry about. What you do need to concern yourself with is hardware and maintenance. A linux subversion box is useless if it has limited hard drive space, low memory, etc. and is even worse if you aren't used to working with linux. Are you comfortable with windows? Is that linux box sitting in a corner out of the way? Don't bend over backwards for that linux machine. The costs will outweigh the benefits. Pick a windows machine with good hard drive space and specs (i.e. can be a server) and put your subversion repository on that. Quote:
Subversion gives you a few different files. The first is the client itself (svn.exe). The client can connect to a repository (local, on a network,with authentication,etc). The next significant file is svnadmin.exe, which allows actually working with the repository. You'll need it to create the repository. Most of the time, you want subversion repositories to be on a server. If you don't rely on apache as a webserver, setting up apache and then configuring it for subversion may seem too much. Which is why subversion gives you svnserve. Svnserve is a server specifically for subversion repositories. You should run it on the commandline. The manual and subversion book should explain the parameters you have to enter on the command line. Alternative, you can create a shortcut or a batch file. Or take a look at: http://www.excastle.com/blog/archive/2005/05/31/1048.aspx EDIT: Don't worry about SSH unless you have it already setup and is widely used. Potentially, your developers could SSH into the subversion server and then work with the command line. Unless your developers use SSH extensively or as part of a protocol, it's not necessary. Quote:
It's that easy. TortoiseSVN makes some client tasks and administration as simple as a few clicks. That means you could set up the server on one machine. Everyone else, on their own machine, uses TortoiseSVN to connect to your repository in a few clicks. It's painless. |
|
#6
|
||||
|
||||
|
Thanks for all the help so far
![]() Yeah I think we will need to use Svnserve as it sounds easier to setup than Apache. Did I install everything in the right place? Subversion is on a different drive U:/, but that means it's in my Start Menu on C:/, should I have installed it from the U:/ drive explicitly? I suppose the repository needs to be created on the remote drive U:/ so that other developers can access it. |
![]() |
| Viewing: Dev Shed Forums > Web Site Management > Development Software > I need some basic advice on using Subversion |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|