For production server systems running under Linux, I've used apache commons daemon to get java apps launched, for example under root to get port 80 and then su'd to run under the app (non-privileged) userid. The advantage is these can be automatically restarted when the server reboots, or services are restarted by operations, etc. Check Google for "jsvc" or "commons daemon" for details.
I haven't yet used this for Clojure apps yet but intend to when deploying them for server production. Should be easy to do, but I'll post on that when I've tried it out. Regards, Adrian. On Sat, May 9, 2009 at 1:12 AM, André Thieme <splendidl...@googlemail.com> wrote: > > On 9 Mai, 00:30, Chris Dean <ctd...@sokitomi.com> wrote: >> How do folks launch their apps? >> >> For building (and maybe deploying) it seems that most people use the >> Java tools (ant, maven, ivy) or have a 10 line shell script. For pure >> Clojure code you don't even necessarily have to have a build step. >> >> But how do you launch your code in a production style setting? > > Depending on what kind of app it is. If it is a desktop application > then a .jar file that can be doubleclicked to run sounds like the > right thing. An alternative would be applets or Webstart. > > For server apps it could be a launch script. > The launch script could be run in a screen. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
