| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
And a newline.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This corrects an oversight in our testing framework where we were
using a local build of Gitano rather than an "installation" for
test purposes. This should result in fewer cases of missed modules,
plugins, skeleton entries, etc.
|
| |
|
|
|
|
|
|
|
| |
It warrants more explanation than is reasonable
in the midst of the rest of the rules,
and allows it to be included in alternative locations
without unnecessary code duplication.
|
| |
|
| |
|
|
|
|
|
| |
Richard spotted a --stdout and I wanted to clean up
some of the logging. All good now.
|
| |
|
|
|
|
|
|
|
|
| |
This plugin supports running git_multimail.py during the
post-receive hook. It uses Lace and Supple to provide simple
but flexible control of the service, and requires sysadmins to
pre-configure the site outside of gitano-admin control which
should ensure a reduction in the abuse-ability of it.
|
|
|
|
|
|
| |
Since supporting git_multimail.py is quite complex, this README
provides documentation. Eventually it might do well to be converted
to a chapter in the admin manual.
|
| |
|
|
|
|
|
|
|
| |
This should be updated whenever a new feature is added to Gitano.
It is not meant to be a full changelog, so only put headline
items in this file please. The first time a change happens
after a new version, please remember to add the new title.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The smart-http interface starts http-backend which calls receive-pack.
Unfortunately we were performing the dangling-HEAD check
after calling receive-pack ourselves,
so when using smart-http we weren't performing the check.
By moving this into the post-receive hook
the check can be performed in smart-http too.
|
| |
|
|
|
|
|
| |
HOME is needed to find the modified git config.
It not being set before now was an oversight.
|
| |
|
|
|
|
|
|
|
|
| |
Because additional git config is now required to use ext:: urls
running git directly is not sufficient
as the HOME variable needs to be set to locate the modified config.
It's simplest to modify the yarns to use $GTT rungit to do this.
|
|
|
|
|
|
|
|
| |
Newer versions of git block the ext:: protocol by default,
so that a repository with submodules may not run arbitrary code.
Whitelisting the ext:: protocol for the test users is the minimum effort
required to make it work again.
|
| |
|
| |
|
|
|
|
|
|
|
| |
In order to make this work, I had to rework password handling in the test
suite, and also redo the http unwrapper to use wget instead of executing the
cgi directly. All yarn IMPLEMENTs which use $GTT runcommand and don't pass the
stdin, *MUST* explicitly use </dev/null to prevent hangs in http mode.
|
| |
|
|
|
|
|
|
| |
When deleting or renaming users, the htpasswd file needs
updating so that we don't leave stale or incorrectly assigned
user credentials around.
|
|
|
|
|
| |
In order to support the sysbranch work I'm doing for the CI, we need
LUA_INIT to get passed through in the environment.
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Basic hook tests which verify preauth commandline and post receive hooks.
|
| |
| |
| |
| |
| |
| | |
This adds POST_RECEIVE properly as a hook. We move the current behaviour into
hook functions, separating out core updates from the Supple hook run, to permit
plugins to interpose behaviour.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This hook is permitted to adjust the command line before it is
passed on to command authorisation. This is needed for a number
of use-cases requested around permitting a plugin to provide domain
specific command line shapes without needing to adjust Gitano's
core command structures.
|
| |
| |
| |
| |
| |
| |
| | |
This adjusts the core gitano module to export gitano.hooks.
In addition, we bump the API version to 1.1.0 since we're adding
in a new API (hooks)
|
| |
| |
| |
| |
| |
| | |
This adds hook names to the gitano.hooks API which is there to
explain what the hook functions should do, and to provide a logical
name for hooks, rather than expecting people to not typo strings.
|