##// 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
hipchat.rst
13 lines | 425 B | text/x-rst | RstLexer
dan
docs: updated docs for integrations, fixes #4137...
r552 .. _integrations-hipchat:
Hipchat integration
===================
docs: updated integrations docs fix #4137
r645 In order to set a Hipchat integration up, it is necessary to obtain the Hipchat
dan
docs: updated docs for integrations, fixes #4137...
r552 service url by:
docs: updated integrations docs fix #4137
r645 1. Log into Hipchat (https://your-hipchat.hipchat.com/)
2. Go to *Integrations* -> *Build your own*
dan
docs: updated docs for integrations, fixes #4137...
r552 3. Select a room to post notifications to and save it
docs: updated integrations docs fix #4137
r645 Hipchat will create a URL for you to use in your integration as outlined in
:ref:`creating-integrations`.