Commit a051dd6a authored by Steve Azzopardi's avatar Steve Azzopardi

Update web terminal note for shared runners

The current documentation suggests that a user can not use his own
runner for a specific group or project. At first I thought this was the
case but it is not true, since we do allow websocket connections on
GitLab.com, this was discovered as part of the investigation on
https://gitlab.com/gitlab-org/gitlab-ce/issues/52611.
parent 4c6ad05c
# Interactive Web Terminals **[CORE ONLY]** # Interactive Web Terminals
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/50144) in GitLab 11.3. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/50144) in GitLab 11.3.
...@@ -9,10 +9,11 @@ is deployed, some [security precautions](../../administration/integration/termin ...@@ -9,10 +9,11 @@ is deployed, some [security precautions](../../administration/integration/termin
taken to protect the users. taken to protect the users.
NOTE: **Note:** NOTE: **Note:**
GitLab.com does not support interactive web terminal at the moment – neither [Shared runners on GitLab.com](../quick_start/README.md#shared-runners) do not
using shared GitLab.com runners nor your own runners. Please follow provide an interactive web terminal. Follow [this
[this issue](https://gitlab.com/gitlab-org/gitlab-ce/issues/52611) for issue](https://gitlab.com/gitlab-org/gitlab-ce/issues/52611) for progress on
progress. adding support. For groups and projects hosted on GitLab.com, interactive web
terminals are available when using your own group or project runner.
## Configuration ## Configuration
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment