rhodecode-enterprise-ce Files · docs/integrations/slack.rst

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.

lisaq - - Load All Authors

File last commit:

r645:c8c27324 default


                r2572:5b07455a

default

Download file

             slack.rst
        
                    20 lines
            
             | 755 B
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / integrations / slack.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        dan
    
docs: updated docs for integrations, fixes #4137...

              r552
            
      .. _integrations-slack:

      Slack integration

      =================

        lisaq
    
docs: updated integrations docs fix #4137

              r645
            
      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:

        dan
    
docs: updated docs for integrations, fixes #4137...

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

        lisaq
    
docs: updated integrations docs fix #4137

              r645
            
      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.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

dan docs: updated docs for integrations, fixes #4137...	r552	.. _integrations-slack:

		Slack integration
		=================

lisaq docs: updated integrations docs fix #4137	r645	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:
dan docs: updated docs for integrations, fixes #4137...	r552
		https://my.slack.com/services/new/incoming-webhook/

lisaq docs: updated integrations docs fix #4137	r645	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.