##// END OF EJS Templates
caches: use individual namespaces per user to prevent beaker caching problems....
caches: use individual namespaces per user to prevent beaker caching problems. - especially for mysql in case large number of data in caches there could be critical errors storing cache, and thus preventing users from authentication. This is caused by the fact that we used single namespace for ALL users. It means it grew as number of users grew reaching mysql single column limit. This changes the behaviour and now we use namespace per-user it means that each user-id will have it's own cache namespace fragmenting maximum column data to a single user cache. Which we should never reach.

File last commit:

r1856:25c48cf5 stable
r2572:5b07455a default
Show More
integrations.rst
55 lines | 1.9 KiB | text/x-rst | RstLexer
dan
docs: updated docs for integrations, fixes #4137...
r552 .. _integrations:
Integrations
------------
project: added all source files and assets
r1
docs: updated integrations docs fix #4137
r645 Rhodecode supports integrations with external services for various events,
dan
docs: updated docs for integrations, fixes #4137...
r552 such as commit pushes and pull requests. Multiple integrations of the same type
docs: updated integrations docs fix #4137
r645 can be added at the same time; this is useful for posting different events to
different Slack channels, for example.
project: added all source files and assets
r1
dan
docs: updated docs for integrations, fixes #4137...
r552 Supported integrations
^^^^^^^^^^^^^^^^^^^^^^
project: added all source files and assets
r1
dan
docs: updated docs for integrations, fixes #4137...
r552 ============================ ============ =====================================
Type/Name |RC| Edition Description
============================ ============ =====================================
:ref:`integrations-slack` |RCCEshort| https://slack.com/
:ref:`integrations-hipchat` |RCCEshort| https://www.hipchat.com/
:ref:`integrations-webhook` |RCCEshort| POST events as `json` to a custom url
docs: added CI integration docs.
r1837 :ref:`integrations-ci` |RCCEshort| Trigger Builds for Common CI Systems
:ref:`integrations-email` |RCCEshort| Send repo push commits by email
dan
docs: updated docs for integrations, fixes #4137...
r552 :ref:`integrations-redmine` |RCEEshort| Close/Resolve/Reference redmine issues
:ref:`integrations-jira` |RCEEshort| Close/Resolve/Reference JIRA issues
============================ ============ =====================================
.. _creating-integrations:
docs: updated integrations docs fix #4137
r645 Creating an Integration
dan
docs: updated docs for integrations, fixes #4137...
r552 ^^^^^^^^^^^^^^^^^^^^^^^
Integrations can be added globally via the admin UI:
:menuselection:`Admin --> Integrations`
docs: updated integrations docs fix #4137
r645 or per repository in each repository's settings:
dan
docs: updated docs for integrations, fixes #4137...
r552
:menuselection:`Admin --> Repositories --> Edit --> Integrations`
docs: updated integrations docs fix #4137
r645 To create an integration, select the type from the list in the *Create New
Integration* section.
dan
docs: updated docs for integrations, fixes #4137...
r552
docs: updated integrations docs fix #4137
r645 The *Current Integrations* section shows existing integrations that have been
created along with their type (eg. Slack) and enabled status.
See pages specific to each type of integration for more instructions:
project: added all source files and assets
r1
.. toctree::
dan
docs: updated docs for integrations, fixes #4137...
r552 slack
hipchat
redmine
jira
webhook
docs: fixed small wanrings/errors during build.
r1120 email
docs: small rst fixes.
r1856 ci