Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #34420

Closed (moved)
Open
Opened Jun 10, 2020 by Hiro@hiro🏄

enable Gitlab backups

I am configuring gitlab backups via cron and the puppet module.

Here is a MR: https://share.riseup.net/#P2Yu4rpQubidQ0V5r7QM1Q

This does the following:

Configure gitlab backups via the puppet module. Will create a backup file every night at 2 am on /srv/backups It will use Gitlab backup command which is a wrapper of the rake task within gitlab rails. More information on: https://docs.gitlab.com/ee/raketasks/backup_restore.html#back-up-gitlab

It also set a cron job to backup gitlab secrets every night at 2 am and place it on /srv/backups.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#34420