Config for forge-allura.apache.org to enable auth for SCM:
In `/etc/apache2/sites-available/allura` add the following to both VirtualHost
sections:
~~~~
::apache
SetEnv GIT_PROJECT_ROOT /var/local/repos/git
SetEnv GIT_HTTP_EXPORT_ALL
AliasMatch ^/git/(.*/objects/[0-9a-f]{2}/[0-9a-f]{38})$
/var/local/repos/git/$1
AliasMatch ^/git/(.*/objects/pack/pack-[0-9a-f]{40}.(pack|idx))$
/var/local/repos/git/$1
<LocationMatch "^/git/">
AddHandler mod_python .py
AuthType Basic
AuthName "Git Access"
PythonAccessHandler /var/local/allura/scripts/ApacheAccessHandler.py
PythonOption ALLURA_AUTH_URL
https://forge-allura.apache.org/auth/do_login
PythonOption ALLURA_PERM_URL
https://forge-allura.apache.org/auth/repo_permissions
PythonOption ALLURA_VIRTUALENV /var/local/env-allura
</LocationMatch>
ProxyPass /git/ !
ScriptAlias /git/ /usr/lib/git-core/git-http-backend/
~~~~
---
** [tickets:#7134] Forking on forge-allura.apache.org should work**
**Status:** code-review
**Milestone:** forge-apr-4
**Labels:** asf
**Created:** Wed Feb 05, 2014 06:44 PM UTC by Dave Brondsema
**Last Updated:** Thu Mar 27, 2014 07:29 PM UTC
**Owner:** Cory Johns
Users should be able to fork https://forge-allura.apache.org/p/allura/git/
Currently you can make a fork, but there's no way to get your code or to push
it back. The 'allura' project on our server there is basically a readonly copy
with pointers to https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git
For forks (and any other type of local project on the server) to work, we could
run git services on the allura-vm host. And probably need some code/config
changes to support having a different checkout URL for the 'allura' repo vs
other repos.
---
Sent from sourceforge.net because [email protected] is subscribed to
https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
