You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Birdsell, John - OIG" <Bi...@oig.dol.gov> on 2010/06/10 12:47:50 UTC

startup questions

Hello,

 

I am new to svn, and have inherited the project of installing and
implementing version control.  Currently we are not using any form of
version control

 

A little background; our current environment set up is, develop on local
machines (win) ftp to test (Unix) on approval, ftp from local to
production (Unix) and we developing in ColdFusion.   The versioning
project was started about 6 months ago and the two people on the
project, a dba and a developer both left a month into it and of course
left no documentation as to their progress.

 

I currently have svn v.1.6.6 installed on our test box.

I have read:  svnbook.red-bean.com for 1.6 and "Pragmatic Version
Control using Subversion 2nd ed." And I'm more confused now than before
I began.  All of the examples seem to have everything on a single box,
and I have been able to set up a test repos on the test box, but I must
be in the svn bin directory as root to execute any command, unlike the
examples that have you executing commands from different directories.
All directories that I set up have group read write execute permissions.


 

Question 1, How should I have groups and users set up so that I can
execute from any directory?

 

I cant find any examples of accessing a repository that is on a
different system UNIX -> Win  or Win -> UNIX.   

 

Question 2, What would the syntax be for that?

 

Question 3, What is the default port for svn?

 

If someone could point me to specific examples or  give any advice it
would be greatly appreciated.

 

Thanks

 

 

John Birdsell

 

IT Specialist 

US Dept of Labor

Office of Inspector General

200 Constitution Ave, NW

Room S5020

Washington, DC 20210

 

(202) 693-7055 

 

Birdsell.John@oig.dol.gov <ma...@oig.dol.gov> 

 


Re: startup questions

Posted by vishwajeet singh <de...@gmail.com>.
On Thu, Jun 10, 2010 at 6:17 PM, Birdsell, John - OIG <
Birdsell.john@oig.dol.gov> wrote:

>  Hello,
>
>
>
> I am new to svn, and have inherited the project of installing and
> implementing version control.  Currently we are not using any form of
> version control
>
>
>
> A little background; our current environment set up is, develop on local
> machines (win) ftp to test (Unix) on approval, ftp from local to production
> (Unix) and we developing in ColdFusion.   The versioning project was started
> about 6 months ago and the two people on the project, a dba and a developer
> both left a month into it and of course left no documentation as to their
> progress.
>
>
>
> I currently have svn v.1.6.6 installed on our test box.
>
> I have read:  svnbook.red-bean.com for 1.6 and “Pragmatic Version Control
> using Subversion 2nd ed.” And I’m more confused now than before I began.
> All of the examples seem to have everything on a single box, and I have been
> able to set up a test repos on the test box, but I must be in the svn bin
> directory as root to execute any command, unlike the examples that have you
> executing commands from different directories. All directories that I set up
> have group read write execute permissions.
>
>
>
> Question 1, How should I have groups and users set up so that I can execute
> from any directory?
>
you need to setup a server and create authorization file to give access to
users, your system users and group are not necessarily the same as
Subversion authorization file

> I cant find any examples of accessing a repository that is on a different
> system UNIX -> Win  or Win -> UNIX.
>
Once you setup server it does not matter whether client is on windows or
linux.

>
>
> Question 2, What would the syntax be for that?
>
Each repository created has format for authorization file inside it so you
can see that for reference

>
>
> Question 3, What is the default port for svn?
>
it's 3980 but I am not sure

>
>
> If someone could point me to specific examples or  give any advice it would
> be greatly appreciated.
>
>
>
> Thanks
>
>
>
>
>
> *John Birdsell*
>
>
>
> *IT Specialist*
>
> US Dept of Labor
>
> Office of Inspector General
>
> 200 Constitution Ave, NW
>
> Room S5020
>
> Washington, DC 20210
>
>
>
> (202) 693-7055
>
>
>
> Birdsell.John@oig.dol.gov
>
>
>



-- 
Vishwajeet Singh
+91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet

Re: startup questions

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jun 10, 2010, at 07:47, Birdsell, John - OIG wrote:

> I have read:  svnbook.red-bean.com for 1.6 and “Pragmatic Version Control using Subversion 2nd ed.” And I’m more confused now than before I began.

Sorry to hear that! I found the Red Bean book quite clear and helpful, starting with no version control background.


> All of the examples seem to have everything on a single box,

I haven't read Pragmatic Version Control but in the Red Bean book that's certainly not the case. See for example:

http://svnbook.red-bean.com/en/1.5/svn.basic.in-action.html#svn.advanced.reposurls


> and I have been able to set up a test repos on the test box, but I must be in the svn bin directory as root to execute any command, unlike the examples that have you executing commands from different directories.

That should not be. What happens otherwise? What are the permissions of the svn command?


> All directories that I set up have group read write execute permissions.
>  
> Question 1, How should I have groups and users set up so that I can execute from any directory?
>  
> I cant find any examples of accessing a repository that is on a different system UNIX -> Win  or Win -> UNIX.  
>  
> Question 2, What would the syntax be for that?

Set up a server:

http://svnbook.red-bean.com/en/1.5/svn.serverconfig.html

Then just access the repository's URL. Depending on what server you choose, your URL might begin with http, https, svn or svn+ssh.


> Question 3, What is the default port for svn?

It depends on the protocol you use:

http: 80
https: 443
svn: 3690
svn+ssh: 22

For any of these you can change the port to something nonstandard if desired.