> > > -----Original Message-----
> > > From: Stefano Mora [mailto:smora_at_eos.pr.it]
> > > Sent: 31 October 2011 10:26
> > > To: 'users_at_subversion.apache.org'
> > > Subject: Browsing folders and SVN
> > >
> > > Hi all,
> > > we'd like to build the following FS+SVN structure:
> > >
> > > - Folder1 (physical folder)
> > > -- Folder2 (physical folder = list of repos)
> > > --- Folder3 (physical folder = repo)
> > > ---- Folder4 (svn folders/files)
> > >
> > > Is it possible?
> > > So far, I defined them but I have errors.
> > > If I type 'svn list http://server:8080/folder1/folder2/'
> > > I recevice the error 'Redirect cycle detected' for URL
> > > If I type 'svn list
> > > http://server:8080/folder1/folder2/folder3' I recevice
> > > the correct svn content.
> > >
> > > We also like to browse the folders by the web browser but
> > > we cannot overlap the svn folder with a <Directory>
> > > declaration. So I'm able to browse the
> > > http://server:8080/folder1/folder2/folder3 items but not
> > > the above ones.
> > >
> > > How can I solve it?
> > > Regards
> > > ----
> > > Ing. Stefano Mora
> > Da: Cooke, Mark [mailto:mark.cooke_at_siemens.com]
> > Inviato: luned́ 31 ottobre 2011 13.47
> > A: Stefano Mora; 'users_at_subversion.apache.org'
> > Oggetto: [SPAM] - RE: Browsing folders and SVN - Trovata
> parola o parole list
> > error nel corpo del testo
> >
> > How do you want to serve your svn content? I assume something
> > like apache? Then you would configure svn to serve 'folder2'
> > as the SVNParentPath [1]. You would need to configure apache to
> > expect 'folder1' as part of the path (in the <Location>
> > directive), that would not be required by subversion.
> >
> > Perhaps you could post the relevant bits of your apache
> > config (if that is what you are using)?
> >
> > ~ mark c
> >
> > [1] http://stackoverflow.com/questions/488778/how-do-i-list-all-repositories-with-the-svnparentpath-directive-on-apachesvn
> -----Original Message-----
> From: Stefano Mora [mailto:smora_at_eos.pr.it]
> Sent: 31 October 2011 14:09
> To: Cooke, Mark; 'users_at_subversion.apache.org'
> Subject: R: RE: Browsing folders and SVN - Trovata parola o
> parole list error nel corpo del testo
>
> I'm sorry: yes, I'm using apache and svn modules.
> We like to handle some repositories in the form:
> <location>/<type>/<company>/<project>/<files>.
>
> Examples physical directories:
> E:/svnroot/dev/cmp1/proj1/files..
> E:/svnroot/dev/cmp1/proj2/files..
> E:/svnroot/deploy/cmp2/proj3/files..
>
> We need to browse the folders under root, folder1 (dev,
> deploy, ..) until cmpX as file system: when we enter into a
> cmpX, we'd like to view all the projects(repositories) and
> then, within a project, all the files.
> http://srv:8080/ - we want to see dev/, deploy/ folders
> http://srv:8080/dev - we want to see cmp1, cmp2, cmp3, .. folders
> http://srv:8080/dev/cmp2 - we want to see all the projects as
> a list of repositories
>
> We need Windows authentication: so we use SSPI.
(aside: SSPI seems unsupported so I moved to mod_ldap which is harder to understand but current once you have got there)
> This is a piece of our httpd.conf file:
>
> <Location /dev/cmp1>
> DAV svn
> SVNListParentPath on
> # SVNPath e:/svnroot/dev/ cmp1/
> SVNReposName "Repository progetti sviluppo cmp1"
> SVNParentPath e:/svnroot/dev/ cmp1/
>
> AuthzSVNAccessFile e:/svnroot/svn-acl
>
> # AuthType Basic
> AuthName "Subversion repository"
> AuthType SSPI
> SSPIAuth On
> SSPIAuthoritative On
>
> SSPIDomain cmp1
> SSPIOmitDomain On # keep domain name in userid string
> SSPIOfferBasic On # let non-IE clients authenticate
> SSPIBasicPreferred Off # should basic authentication
> have higher priority
> SSPIUsernameCase lower
> Require valid-user
> </Location>
>
> We will create other sections for comp2 .. companies.
>
> When we point to svn folders, we see the files by the SVN
> system: we need to view the upper folders.
>
Sorry, now I understand what you want I am not sure how to do it. When you add the <Location "url"> DAV svn sections, subversion will try to serve all paths that start with "url" so you cannot expose anything below that path.
However, you should be able to expose things short of that path using normal apache stuff. What do you want to be able to do with the files in the intermediate folders? Just read-only access (in which case investigate mod_dir at http://httpd.apache.org/docs/2.0/mod/mod_dir.html) or more complex WebDAV actions?
~ mark c
Received on 2011-10-31 15:43:22 CET