Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gitlab-mattermost gitlab-mattermost
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-mattermostgitlab-mattermost
  • Issues
  • #67
Closed
Open
Created May 04, 2016 by Ian Tien@it33Maintainer

[Help Wanted] Document best practice for GitLab-specific CLI tool configuration to GitLab Mattermost Admin Guide

While GitLab omnibus is set up to manage Mattermost via the gitlab.rb file and a custom layout of Mattermost files, some community members want more control by using the Mattermost CLI tool, which requires additional configuration steps because of the GitLab omnibus layout.

This request is to ask help from the community to make a merge request to document the additional steps in the GitLab Mattermost Admin Guide, which can be verified by the GitLab omnibus team and included in a future release.

This issue is cross-posted to the GitLab Mattermost forum

Assignee
Assign to
Time tracking