incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Chirila <schir...@gmail.com>
Subject Allura setup with Active Directory
Date Sat, 21 Sep 2013 21:09:14 GMT
Hi,

I'm currently trying to setup the allura at work. I'm currently using the
vagrant image for this purpose.
Here's what I'm trying to achieve (objective):
1. Users at work should be able to register/login to allura with their
Active Directory credentials (through LDAP)
2. Users should be allowed to create projects in allura and allow other
people to join their development efforts.
3. Authenticated users should be able to use git to pull, push changes to
the repository.
4. The git repository will be, at one point in the future, integrated with
Jenkins. So proper setup should be done for Git.

Main challenges with current version of Allura (via vagrant setup):
1. LDAP setup with schroot is not clear enough. Maybe documentation should
be updated to explain also the logic of the steps (like fuse driver setup,
ldap configuration, etc.). For example why the linking of /git and /hg to
/var/chroots/scm was done. It doesn't mention where to mention these /git
and /hg after this. (should they be set in the ini somewhere or it's
programmatically used when ldap is used).
2. GIT repository setup. What needs to be changed in the .ini, to allow
users to access the git repository and to make changes to it (push)
considering the setup above. Currently it's not documented how the
scm.repos.root needs to be set in case of a schroot setup.
3. Additional setup steps regarding running it from vagrant. Which ports
need to be forward, to make  git access work.

This is so far what I'm trying to achieve.
Thanks to anyone reading this and having some insights to share on the
above matter.

Best regards,
Stefan Chirila

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message