Dear developers, with Ubuntu 14.04 (at least today) it is not necessary to compile a patch to make NParentPath be recursive as reported in https://forge-allura.apache.org/docs/getting_started/scm_host.html because the actual svn version installable from its official repositories (svn, version 1.8.8 ) it is able to manage recursively the svn repository. The only problem is that it works: a) in parallel from the parent directory b) the children directory have to be the svn repositories.
This is a problem for Allura because of its way of creating and managing projects repositories. It stores them in ../svn/p/project_name1/svn ../svn/p/project_name2/svn In fact setting NParentPath= ../snv/p/ the children are project_name1 and project_name2, which are not svn repositories, but just folders containing the svn repository folders. If instead if I copy the repositories up to the project_name folders, I can access them via HTTP without any problem. Thus to avoid to patch the source of Subversion 1.7's mod_dav_svn, recompile and install and just to use the latest version, it would be much better to have under the ../svn root directory or ../svn/p/ (why not eliminate such not useful intermediate directory) the project_name directories as snv repositories. This will solve a lot of problems. Is this something that can be managed via some settings or some code has to be modified? Thanks in advance Livio Mazzarella -----Original Message----- From: Dave Brondsema [mailto:d...@brondsema.net] Sent: giovedì 23 luglio 2015 20:25 To: Livio Mazzarella; dev@allura.apache.org Subject: Re: Some Allura problems. (I got this email privately, and am replying on the dev list, with Livio's permission) I haven't used the ldap/ssh/fuse setup myself. It's a pretty complicated approach. If all you need is users to match between Allura and repo access, that approach isn't needed. You can use the approach documented at https://forge-allura.apache.org/docs/getting_started/scm_host.html One downside I should point out is that if you want to use SVN repos, you'll need to patch/compile SVN. Or just have your config file list out all the repos that you use, and update it when you make a new project/repo. If you want LDAP for some other reason, you can still use the approach at https://forge-allura.apache.org/docs/getting_started/scm_host.html instead (avoid all the chroot/fuse complex stuff). It just integrates Allura with your repos, and backs with any auth.method choice. If you do want to use LDAP (which again, is not necessary if just want Allura & repo auth to be integrated) the instructions at https://forge-allura.apache.org/docs/getting_started/installation.html#using-ldap will be useful. Specifically check the auth.ldap.server setting. You might need ldap:// instead of ldaps:// Let us know how it goes! If you have further questions in getting it set up, please do reply. (To the dev list is best) On 7/21/15 2:40 PM, Livio Mazzarella wrote: > Dear Dave, > > > > sorry if I am using your private e-mail, but it was the simplest way > for me to contact you. Let me know if eventually I can still use such > way or if you prefer another one. > > > > I have installed the Allura latest version (production setup) in on a "fresh" > Ubuntu 14.04.2 LTS server and I have problem with user's > authentication. When I am using auth.method=local everything is > working fine. My problems start when I am trying to use Allura with > LDAP authentication ( this because I would like to use the Allura > registration to automatically create LDAP users to manage the repository > access). > > I was not able to make that working at all, both using the method > suggested on > https://forge-allura.apache.org/docs/getting_started/scm_host_ssh.html > #scm-hosting-ssh, using schroot and debootstrap, or installing LADP > directly on the server. In both cases when I try to login with an > already (locally) registered user or to register a new user, I get the > error "SERVER_DOWN: {'desc': "Can't contact LDAP server"}. > > The LDAP server is correctly working and the database correctly > initialized ( I just installed phpldapadmin to quickly check that: a screen > shot is attached too). > > > > In the attached pdf file the weberror trace back is reported. I also > attached the development.ini and the modified ldap-setup.py file I > have used to set up LDAP. Why is the "open_ldap_config = > string.Template(." not used? Where, eventually, these setup have to be > included, if they are responsible for the error. > > > > Tanks in advance for any possible suggestion to solve that issue. > > > > PS. Our goal is to use Allura for an open source project we have been > developing in the field of building energy performance simulation tools. > > > > Prof. Livio Mazzarella > > > > Professore Ordinario di Fisica Tecnica Ambientale > > Politecnico di Milano - Dipartimento di Energia > > Coordinatore del Gruppo di Ricerca BEES "Buildings' Environment and Energy > Systems" > Responsabile del Laboratorio di Acustica > -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
