[tor-bugs] #5204 [Company]: Set up VM running Apache for Atlas/TorStatus

[Tor Bug Tracker & Wiki]

#5204: Set up VM running Apache for Atlas/TorStatus
---------------------+------------------------------------------------------
 Reporter:  karsten  |          Owner:  phobos
     Type:  task     |         Status:  new   
 Priority:  normal   |      Milestone:        
Component:  Company  |        Version:        
 Keywords:           |         Parent:  #5189 
   Points:           |   Actualpoints:        
---------------------+------------------------------------------------------

Comment(by karsten):

 Replying to [comment:1 phobos]:
 > After thinking about this, here are my thoughts:
 >
 > 1. if the site is static, we can serve it off the current static-content
 webservers.

 Yes, I think that would work.  Three questions remain:

 1. We wouldn't hurt same origin policy if the static HTML lives on
 atlas.tpo and the data comes from somewhereelse.tpo, right?

 2. Would hellais be able to update the static content?  (I wouldn't
 need/want access to the static pages, nor would atagar.)

 3. Would the static pages be available as http://atlas.tpo/index.html ?

 > 2. the python bits can run on the current wgsi-serving webservers.

 Not sure about that.  There will be two Python bits: 1) a Python cronjob
 that requires a few gigs of disk space and a database and 2) a JSON-
 serving Python thing that can get plugged into Apache.  I'd guess 1
 shouldn't live on the current WGSI-serving webservers.  1 and 2 should
 live on the same host.

 > do you still need a vm?

 We don't need a VM for the Python parts now, but maybe in a month or two
 from now.  I can open a new ticket then.

 > if everything is pushed to appropriate git repos, weasel or I can just
 git pull and update the services.

 I can maintain this service, possibly together with atagar.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5204#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online