Skip to content
Snippets Groups Projects

Update databases.md

Merged gitlab-qa-bot requested to merge github/fork/zzet/patch-4 into master

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Created by: dzaporozhets

    Can you explain please how this related?

    By Administrator on 2013-03-24T10:05:55 (imported from GitLab project)

    By Administrator on 2013-03-24T10:05:55 (imported from GitLab)

  • Created by: coveralls

    Coverage remained the same when pulling 159cd0d7 on zzet:patch-4 into 979dcdba on gitlabhq:master.

    View Details

    By Administrator on 2013-03-24T10:30:26 (imported from GitLab project)

    By Administrator on 2013-03-24T10:30:26 (imported from GitLab)

  • Created by: zzet

    @randx of course.

    User install gitlab according to instructions. The manual is written to give rights to the user gitlab on database gitlabhq_production. Due to the fact that at the moment is the only current user git it is desirable to update the documentation.

    It is clear that he set up gitlab befor your changes for the users, but in order to avoid problems in the future, it must be updated.

    Thx.

    By Administrator on 2013-03-24T10:16:34 (imported from GitLab project)

    By Administrator on 2013-03-24T10:16:34 (imported from GitLab)

  • Created by: dzaporozhets

    @zzet So Postgres ROLE linked with system user. So if we dont have gitlab system user we cannot use gitlabhq_production

    By Administrator on 2013-03-24T10:31:34 (imported from GitLab project)

    By Administrator on 2013-03-24T10:31:34 (imported from GitLab)

  • Created by: zzet

    @randx of course! And of course you know that now there is no user gitlab

    If user prefer trust auth method it command for they are impossible: sudo -u git -H psql gitlabhq_production

    Then they run bundle exec rake db:migrate RAILS_ENV=production can be some problems with trust auth methods

    By Administrator on 2013-03-24T10:44:29 (imported from GitLab project)

    By Administrator on 2013-03-24T10:44:29 (imported from GitLab)

  • Created by: coveralls

    Coverage remained the same when pulling 4cc27fd9 on zzet:patch-4 into 979dcdba on gitlabhq:master.

    View Details

    By Administrator on 2013-03-24T10:58:36 (imported from GitLab project)

    By Administrator on 2013-03-24T10:58:36 (imported from GitLab)

  • Created by: dzaporozhets

    @zzet yeap. Thank you for fix

    By Administrator on 2013-03-24T10:44:10 (imported from GitLab project)

    By Administrator on 2013-03-24T10:44:10 (imported from GitLab)

  • Created by: zzet

    @randx Thank you.

    By Administrator on 2013-03-24T10:44:49 (imported from GitLab project)

    By Administrator on 2013-03-24T10:44:49 (imported from GitLab)

Please register or sign in to reply
Loading