ActionCable

Note: ActionCable is experimental, and enabling it in the in-app mode also enables experimental features.

This service is disabled by default. To enable:

actioncable['enable'] = true

By default, ActionCable is run as a separate Puma server that only handles websocket connections. To run ActionCable on the existing Puma web server:

actioncable['in_app'] = true

Note: Action Cable is currently not supported for the Unicorn web server in GitLab.

Configuring the worker pool size

ActionCable uses a separate thread pool to handle the websocket connections. The number of threads can be configured using the actioncable['worker_pool_size'] option.

Help & feedback

Docs

Edit this page to fix an error or add an improvement in a merge request
Create an issue to suggest an improvement to this doc
Show and post comments to review and give feedback on this doc

Product

Create an issue if there's something you don't like about this feature
Propose functionality by submitting a feature request
Join beta testing to help shape new features

Feature availability and product trials

View pricing to see all GitLab tiers and features, or to upgrade
GitLab Gold Free-trial to try all features in GitLab.com
GitLab Ultimate Free-trial to try all features in GitLab self-managed

Get Help

If you didn't find what you were looking for, search the docs.

If you want help with something specific, and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).

Request support