| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
By editing config/memcache.yml you may now define several hosts/ports.
The default still applies: a single Memcache server on localhost
|
|
|
|
| |
Introducing Gitorious.on_config, which simplifies this.
|
|
|
|
| |
Set up indexing information after the app has been loaded.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Ultrasphinx plugin has been abandoned, so we're switching to
ThinkingSphinx instead. The good news is that we're still using the
same search engine, and that all the internal indexing/searching logic
has been preserved through the rewrite.
However, if you maintain your own server, you will need to make a few
changes. The ultrasphinx: rake tasks no longer exist, but have been
replaced by thinking_sphinx tasks:
- rake thinking_sphinx:config generates the Sphinx configuration file
- rake thinking_sphinx:index indexes the Sphinx data rake
- thinking_sphinx:rebuild stops, reindexes and starts Sphinx rake
- thinking_sphinx:reindex reindexes without re-generating a
configuration file
- thinking_sphinx:stop stops Sphinx
- thinking_sphinx:start starts Sphinx
- thinking_sphinx:running_start stops Sphinx if it's running and then starts
it
|
|
|
|
|
|
| |
* RAILS_ROOT -> Rails.root (Pathname instance)
* RAILS_ENV -> Rails.env
* RAILS_DEFAULT_LOGGER -> Rails.logger
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Until this commit, a user with permissions granted to the user himself
would not be allowed to:
- resolve merge requests
- administer a repository
Furthermore, while reviewing Merge Request 217, the following issues
arose, which are resolved here:
- the script/ldap_authorization.rb script is not really useful
- explain what @authorizer is in [ldap_]group_authorization.
|
|
|
|
|
| |
A cache expiry can be defined in authentication.yml to have Gitorious
cache the usernames which are members of a group.
|
|
|
|
|
|
|
|
| |
Auto registration of user accounts would fail if no email address is
found in LDAP. We will now construct a synthetic address in these
cases, to ensure users are able to log in.
It would make sense for such users to add a valid email address afterwards.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Also some minor things:
- don't throw an error when viewing a user without LDAP group memberships
- don't debug LDAP output to stdout
|
|
|
|
|
|
| |
When using LDAP groups for authorization, we now support specifying a
different DN when searching for groups. By default, the same base_dn
as is used for authentication is used.
|