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
  • #31377

Closed (moved)
Open
Opened Aug 08, 2019 by Philipp Winter@phw

Create a GetTor survival guide

The anti-censorship team maintains service-specific "survival guides". The point of these guides is that somebody who's not a maintainer should be able to perform basic maintenance tasks if the main developer is not available. Needless to say, these guides are only useful if more people than just the maintainer have access to a service. In case of GetTor, hiro and phw currently have access to GetTor's machine.

Let's create a survival guide for GetTor. This survival guide should explain how one would:

  • Redeploy GetTor (e.g., after fixing a bug in the code)
  • (Re)start GetTor
  • Update the Tor Browser binaries that GetTor serves
  • Analyse log files
  • ...anything else?
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#31377