##// 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:

r645:c8c27324 default
r2572:5b07455a default
Show More
slack.rst
20 lines | 755 B | text/x-rst | RstLexer

Slack integration

To set a Slack integration up, it is first necessary to set up a Slack webhook API endpoint for your Slack channel. This can be done at:

https://my.slack.com/services/new/incoming-webhook/

Select the channel you would like to use, and Slack will provide you with the webhook URL for configuration.

You can now create a Slack integration as outlined in :ref:`creating-integrations`.

Note

Some settings in the RhodeCode admin are identical to the options within the Slack integration. For example, if notifications are to be sent in a private chat, leave the "Channel" field blank. Likewise, the Emoji option within RhodeCode can override the one set in the Slack admin.