Sean, Because wave uses Jetty as a client-end server, you would need to run wave on some other port and proxy the requests to it through apache (or alternative load balancing proxies). Possibly as part of the proxying you could remap the paths from /wave/ to /. Alternatively in src/org/waveprotocol/box/server/ServerMain.java you can find the mappings in each call of server.addServlet, so could add "/wave/" to the front of them.
It wouldn't be very difficult from there to extend it to a config file option. (I could look into this when I next get some free time (might be a week or two)). The main thing you will need to be careful with is how you handle the websocket traffic. You will either need to proxy that as well, or make the websocket listen on a different port and link that directly to the jetty websocket port. Ali. On 27 Nov 2012 22:09, "Sean Wendt" <[email protected]> wrote: > Hi Ali, > > I run another Rails instance and a NodeJS instance on the same server, > which are proxied through Apache on port 80. The server mustn't public > but is accessible through an SSH tunnel, so it's convenient to have > each in their own directory. > How difficult do you think the changes for running wave in a > subdirectory would be? > > Sean > > On Tue, Nov 27, 2012 at 8:40 PM, Ali Lown <[email protected]> wrote: > > Hi Sean, > > > > There isn't an option to change the location of the resources currently, > > since Jetty is assumed to have full control of the subdomain wave is > > running at. > > > > Is there a reason to run at /wave/ rather than a subdomain? > > > > Ali > > On 27 Nov 2012 18:25, "Sean Wendt" <[email protected]> wrote: > > > >> Hello everyone, > >> > >> I am just getting started setting up a wave instance, which is > >> supposed to be running under http://localhost/wave . > >> Since paths to images etc. are absolute e.g. /static/logo.png , they > >> cannot be found at /wave/static/logo.png > >> Setting http_frontend_public_address or http_frontend_public_address > >> seems to have no effect. > >> Am I missing something? Where is the option to configure the path to > >> the frontend? > >> > >> Regards, > >> Sean > >> >
