Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gettor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • GetTor Project
  • gettor
  • Issues
  • #78
Closed
Open
Created Mar 08, 2021 by Cecylia Bocovich@cohoshOwner

Simplify process to restart GetTor

Right now our Survival Guide says that to restart GetTor, one simply needs to run /home/gettor/gettor/bin/gettor_service \[start|restart\], however this actually needs to be run from where the gettor repository is checked out in order to actually work because it uses relative paths:

case "$1" in
start)
   twistd3 --python=scripts/gettor --logfile=log/gettor.log --pidfile=gettor.pid

This has caused some confusion (for example in #77 (closed)) so we should alter how we do this. BridgeDB "solves" this slightly differently by defining the production environment in a separate bridgedb-admin repository.

I'm not sure we want to do that here, and I'm also not sure what https://gitlab.torproject.org/tpo/anti-censorship/gettor-project/gettor-ansible is for.

Assignee
Assign to
Time tracking