Right now I'm running about a half dozen instances of Jetty (one per site). I'm starting them with java -jar ..., and stopping them with kill -9, which I think is a total hack. To find out what's running, I do a ps aux | grep jetty. Seriously? In 2009?
With Glassfish (or Geronimo or equivalent), I get a nice interface and I can deploy pretty easily. I can see exactly what's going on. I can start and stop servlets easily, and I can set things up to restart automatically on server reboot (instead of writing a shell script). And I'm hoping that despite the higher overhead of Glassfish, that when I get enough sites in there it will be lower than running that many separate instances of Jetty. There may be other things I'd like to play with as well (access control, etc.). The thing that holds me back is that when I deploy multiple sites to Glassfish, a site like mysite.com is actually deployed to mysite.com/mysite. That extra context in the path is a showstopper. But I have been unable to figure out how to get rid of it. I'm open to other suggestions, but there has to be some way for me to host multiple sites with some sort of interface and an easy way to deploy, restart, monitor, etc. them. Chas. Timothy Perrett wrote: > > Phew :) > > Out of interest, why do you want to use glashfish rather than jetty? > > Tim > > On 16/03/2009 10:08, "Charles F. Munat" <[email protected]> wrote: > >> Just Jetty on the server. Maven/Jetty while developing. (I'm not that >> dumb.) :-) >> >> Chas. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
