##// END OF EJS Templates
upstream » kallithea
RSS

Clone from https://kallithea-scm.org/repos/kallithea

TurboGears2 migration: update ini files for error email settings...
TurboGears2 migration: update ini files for error email settings Error emails are now handled by backlash, which is configured through TurboGears2's ErrorReporter. ErrorReporter expects different configuration key names than Pylons did, moreover under a new 'trace_errors' namespace. Since some of the email-related settings are shared between application and error emails, we cannot just rename the existing settings (it would be very odd to have application settings under a 'trace_errors' namespace). Requiring the user to duplicate its settings is also undesirable. Instead, use 'get' to populate the trace_errors namespace based on the existing settings we already had. Unfortunately, 'get' expects the setting to be actually present, so we need to provide an out-of-the-box value for the error-related email settings or there will be an error at startup. We use empty values because there is no realistic default value we can provide.
Søren Løvborg - - Load All Authors

File last commit:

r5425:5ae8e644 default
r6529:b4c27fe6 default
Show More
statistics.rst
31 lines | 1.2 KiB | text/x-rst | RstLexer
/ docs / usage / statistics.rst
History | Annotation | Raw |Copy content |Copy permalink

Repository statistics

Kallithea has a repository statistics feature, disabled by default. When enabled, the amount of commits per committer is visualized in a timeline. This feature can be enabled using the Enable statistics checkbox on the repository Settings page.

The statistics system makes heavy demands on the server resources, so in order to keep a balance between usability and performance, statistics are cached inside the database and gathered incrementally.

When Celery is disabled:

On each first visit to the summary page a set of 250 commits are parsed and added to the statistics cache. This incremental gathering also happens on each visit to the statistics page, until all commits are fetched.

Statistics are kept cached until additional commits are added to the repository. In such a case Kallithea will only fetch the new commits when updating its statistics cache.

When Celery is enabled:

On the first visit to the summary page, Kallithea will create tasks that will execute on Celery workers. These tasks will gather all of the statistics until all commits are parsed. Each task parses 250 commits, then launches a new task.