Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab Chart GitLab Chart
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 652
    • Issues 652
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 41
    • Merge requests 41
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • charts
  • GitLab ChartGitLab Chart
  • Issues
  • #620
Closed
Open
Issue created Jul 24, 2018 by Matthew Cooper@mwcoop

Configuration for smaller deployments

While I understand the goals of high availability and scalable installations, some of us really need nothing more than what the old Omnibus chart provides. Unfortunately, with that becoming deprecated, it would be very nice to have a configuration example for smaller deployments.

In my particular case, we are a non-profit that cannot afford a large infrastructure. Having a config that gives something equivalent to Gitlab-Omnibus (e.g. 2VCPU, 4GB memory) would be great. These numbers aren't critical.

Assignee
Assign to
Time tracking