[tor-bugs] #13089 [Onionoo]: use an embedded web server/servlet engine for Onionoo

[Tor Bug Tracker & Wiki]

#13089: use an embedded web server/servlet engine for Onionoo
-----------------------------+-----------------
     Reporter:  iwakeh       |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  minor        |  Milestone:
    Component:  Onionoo      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by karsten):

 Replying to [comment:2 iwakeh]:
 > Well, easier deployment and an easier configuration, of course.

 Okay.

 > The performance ought to be fine for all, Jetty was used all along for
 Hudson/Jenkins installations,
 > and I could witness that this setup could handle many, many projects and
 users.
 > Embedded tomcat is used by SonarQube. Projects like Solr think about
 switching to Jetty or Netty.
 >
 > The performance of the older versions available in wheezy should be
 fine, too,
 > but of course newer ones will be better. (Btw, wheezy only contains
 older Sonar, not SonarQube.)

 Okay.

 > It's sort of state-of-the-art to provide the all in one jar for an
 application without server
 > configuration/deployment.

 We could provide a jar that, by default, listens on 8080.  People could
 then decide to put it behind an Apache or make it listen on port 80
 directly.  We cannot do the latter, because running a service on a Tor
 machine must not depend on being root, not even when it drops privileges
 after opening the socket.  Plausible?

 > Is it a goal for the Onionoo project to have many servers running?
 > If so, ease of configuration and deployment should be a high priority.

 I surely wouldn't mind other people to run their own instances of Onionoo.
 For example, I'd love to see you running one and have Onionoo clients list
 that as fallback alternative if onionoo.torproject.org is down.  Though
 I'm not sure if this ticket is the main barrier, because the real trick is
 to initialize a new Onionoo instance with years of Tor network archives.
 But that shouldn't stop us here.  Let's make it easier to configure and
 deploy Onionoo, regardless of how many instances there will be.

 Which of the three (embedded Tomcat, Jetty, Netty) should we try out, and
 why?  And would you be willing to submit a patch?

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