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
  • Issues
  • #1850

Closed
Open
Created Oct 27, 2012 by Administrator@rootOwner

doc/installation.md 3.0.3 bug

Created by: worxco

I did 2 fresh installs on 10/25/12.

In both cases, it was done with mysql.

There are commands early in the process (step 5) that

  • create DB
  • create User
  • grant permissions to user on DB

Later in the process (Step 6 - Setup application) the command:

  • sudo -u gitlab bundle exec rake gitlab:app:setup RAILS_ENV=production

fails. By dropping the DB created in step 5, and re-runing this command, all works fine.

This was installed on Debian 6 64bit, fresh install, with update / upgrade process run prior to install.

I would suggest that either the gitlab:app:setup code be altered to recognize an existing DB, or add instructions to drop the DB as part of the "Setup application" step.

Assignee
Assign to
Time tracking