search

ohmage / server

The ohmage server application.
37 stars 25 forks source link

root the server at / #329

Closed jshslsky closed 10 years ago

jshslsky commented 12 years ago

cf. cens/ohmageFrontEnd#253

In order to support URIs that are not rooted at /app (i.e., /api/omh/v1.0 for Open mHealth), the server application needs to be packaged up as ROOT.war so it can be served up from /.

jeroen commented 12 years ago

Can you elaborate? I don't completely understand what it is you want to do.

It is generally better to mount it at /app and then have an alias or proxy like apache2 or nginx that maps / to /app or so. Hijacking root can potentially result in conflicts with other .war apps hosted on the same tomcat.

jshslsky commented 12 years ago

Basically we want to support multiple directory paths for the server. This issue is a result of me wanting to document it during our Open mHealth mini hack-a-thon. Agree with you about not wanting to hijack root.

marc-schwartz commented 12 years ago

Seems like the point here is to have the app not assume any specific context path, but be flexible to any context path (yes, even root). I can see a use-case for root: Amazon Elastic Beanstalk or Heroku Deployments, where you don't get apache or lighttpd to proxy with.