| Commit message (Collapse) | Author | Age |
|
|
|
| |
it will be in the config.
|
|
|
|
| |
a leading slash.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows running gitweb as a separate user without needing to allow it
read access to gitosis-admin.git. Running as separate user will still most
likely require a ``chgrp www-data`` of the relevant repositories, but
nothing not already decided public needs to be exposed.
Existing gitweb users will need to adjust their gitweb.conf to point to
the new location of the projects.list file.
Removing the old projects.list from
~git/repositories/gitosis-admin.git/projects.list is safe once gitweb
has switched to using the new location.
|
|
|
|
|
|
| |
Without this, it would need a separate push to gitosis-admin.git,
after the repository is autocreated, to get it to show up and be
anonymously usable.
|
|
|
|
|
|
|
|
|
|
| |
Creation is in gitosis.serve and not directly in repository.init(),
because that's the location that can tell what part of the directory
tree is allowed to be missing. Made the reconstructed git command
include the extension as that was easier to do.
haveAccess return value is now tuple, to preserve information on what
parts of the path can be missing.
|
|
|
|
|
|
| |
The repository autocreation functionality ends up sending the
stdout to the client side, and there a very confused git push
can't make any sense of the protocol.
|
|
|
|
|
|
| |
Confusion between pathnames with extensions and without made
gitosis-serve confused when it needs to create a repository
and when not.
|
| |
|
| |
|
| |
|
| |
|
|
|