[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9425 [BridgeDB]: Create and document a better BridgeDB (re)deployment strategy

#9425: Create and document a better BridgeDB (re)deployment strategy
--------------------------+-------------------------------
     Reporter:  isis      |      Owner:  isis
         Type:  task      |     Status:  needs_information
     Priority:  normal    |  Milestone:
    Component:  BridgeDB  |    Version:
   Resolution:            |   Keywords:  deploy,doc
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+-------------------------------

Comment (by isis):

 I created ticket #9595 for setting up a new git repo, `admin/bridgedb-
 admin`, for collaborating on maintenance tasks, keeping sysadmin notes,
 deployment scripts and configs, etc. If you would like to help with these
 things, please add yourself to the CC list on that ticket.

 This repo should contain:
   * ponticum-specific deployment things, such as config files for the
 BridgeDB server (e.g. bridgedb.conf and the setup.cfg file) and deployment
 scripts (e.g. deploy.sh)
   * maintainer/sysadmin notes. For example, if I log in, decide that
 bar.sh is cruft because it hasn't been touched in two years, and delete
 it, I would make a note of it somehow in this repo. This way, when so-and-
 so comes along and says "wat? who deleted bar.sh that is part of <insert
 obscure undocumented thing in some other repository> that gets rsync'd
 once every 4 years on leap day?!" any of us can point back and see what
 happened, when, and why. And etc.

 This repo should ''not'' contain:
   * anything sekrit.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9425#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs