Administrator Docs

Learn how to administer your self-managed GitLab instance.

GitLab has two product distributions available through different subscriptions:

You can install either GitLab CE or GitLab EE. However, the features you’ll have access to depend on the subscription you choose (Core, Starter, Premium, or Ultimate).

Note: GitLab Community Edition installations only have access to Core features.

GitLab.com is administered by GitLab, Inc., therefore, only GitLab team members have access to its admin configurations. If you’re a GitLab.com user, please check the user documentation.

Note: Non-administrator users don’t have access to GitLab administration tools and settings.

Installing and maintaining GitLab

Learn how to install, configure, update, and maintain your GitLab instance.

Installing GitLab

Configuring GitLab

Customizing GitLab’s appearance

Maintaining GitLab

  • Raketasks: Perform various tasks for maintenance, backups, automatic webhooks setup, etc.
  • Operations: Keeping GitLab up and running (clean up Redis sessions, moving repositories, Sidekiq MemoryKiller, Unicorn).
  • Restart GitLab: Learn how to restart GitLab and its components.
  • Invalidate markdown cache: Invalidate any cached markdown.

Updating GitLab

Upgrading or downgrading GitLab

GitLab platform integrations

  • Mattermost: Integrate with Mattermost, an open source, private cloud workplace for web messaging.
  • PlantUML: Create simple diagrams in AsciiDoc and Markdown documents created in snippets, wikis, and repos.
  • Web terminals: Provide terminal access to your applications deployed to Kubernetes from within GitLab’s CI/CD environments.

User settings and permissions

Project settings

Repository settings

Continuous Integration settings

Git configuration options

Monitoring GitLab

Performance Monitoring

Analytics

  • Pseudonymizer: Export data from GitLab’s database to CSV files in a secure way.

Troubleshooting

Support Team Docs

The GitLab Support Team has collected a lot of information about troubleshooting GitLab instances. These documents are normally used by the Support Team itself, or by customers with direct guidance from a Support Team member. GitLab administrators may find the information useful for troubleshooting, but if you are experiencing trouble with your GitLab instance, you should check your support options before referring to these documents.

Warning: Using the commands listed in the documentation below could result in data loss or other damage to a GitLab instance, and should only be used by experienced administrators who are aware of the risks.