News for hackers. Stuff that matters.
Re:How We Deploy Our Clojure Services by arohner on Thursday August 26, 2010 @04:24PM (#1637059)
We built our own .deb containing all our bits, that depends on external dependencies. The .deb recipe is checked into source. Our deploy process is

    1) compile the .deb.
    2) spawn a new, empty EC2
    3) apt-get the .deb
    4) lein daemon start (http://github.com/arohner/lein-daemon)
Re:How We Deploy Our Clojure Services by kyleburton on Thursday August 26, 2010 @04:49PM (#1637124)
Ah, lein-daemon - didn't know about that, thanks!
Re:How We Deploy Our Clojure Services by rjurney on Thursday August 26, 2010 @05:05PM (#1637165)
Clojure is very interesting to me as a way to build and deploy services backed by machine learning. Interesting enough to make me learn LISP :)

In particular, two libraries are enormously useful:

http://github.com/bradford/infer http://github.com/afeinberg/clomert

You can use Hadoop with infer to build your model, fill a Voldemort cluster from Hadoop directly, then also serve your model using infer. All with very little code. That is mucho win.

Re:How We Deploy Our Clojure Services by jacquesm on Thursday August 26, 2010 @05:32PM (#1637222)
Isn't that a huge obstacle to overcome to get clojure to become self-hosting? After all, the fact that it has access to java's libraries is a huge plus.
Re:How We Deploy Our Clojure Services by fogus on Thursday August 26, 2010 @07:13PM (#1637453)
Even when Clojure is bootstrapped it will still maintain an extremely strong level of interop with Java (on the JVM flavor of course).