Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
torflow
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 49
    • Issues 49
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar

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.

  • The Tor Project
  • Network Health
  • torflow
  • Issues
  • #24088

Closed
Open
Opened Oct 31, 2017 by Sebastian Hahn@sebastian

Remove setup.sh

Setting up a real bwauth shouldn't hide steps from the operator. It's important the operator knows what software plays a part, which parts won't get updated by themselves, etc. setup.sh hides all that from the operator and makes bad assumptions on top (it forces installation of deprecated dependencies that touch the network like an old version of pip and peep which has also been deprecated gets installed needlessly as well).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/network-health/torflow#24088