Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #31377

Closed (moved)
(moved)
Open
Created 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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking