Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Merge requests
  • !1785

Merged
Created Oct 24, 2012 by Administrator@rootOwner

Refer developers to the vagrant vm and remove out of date documentation.

  • Overview 2
  • Commits 1
  • Changes 2

Created by: dosire

The best way to develop for Gitlab is to use the GItlab Vagrant virtual machine. This PR updates all the documentation to point to the vm. This will make it easier for new people to contribute.

Existing documentation that is out of date (the list of packages to install) or that doesn't work on the VM (using foreman to start gitlab) is removed.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/dosire/update-developer-documentation