Opened 10 months ago

Last modified 5 months ago

#31377 new task

Create a GetTor survival guide

Reported by: phw Owned by:
Priority: Medium Milestone:
Component: Applications/GetTor Version:
Severity: Normal Keywords: survival-guide
Cc: cohosh, gaba, traumschule, hiro, phw Actual Points:
Parent ID: Points: 0.5
Reviewer: Sponsor:


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?

Child Tickets

Change History (2)

comment:1 Changed 8 months ago by cohosh

cc'ing cohosh on open GetTor tickets.

comment:2 Changed 5 months ago by cohosh

Updating this to say that most of these are accounted for. I believe what we have left is to document what happens when we call export_stats as well as any log file processing. That might also be in progress though :)

Here's the current survival guide:

Note: See TracTickets for help on using tickets.