Re: Current state of the art in Web deployment?

2013-08-19 Thread Phil Hagelberg
On Saturday, August 17, 2013 4:51:34 PM UTC-7, Mark Mandel wrote: > > On Sun, Aug 18, 2013 at 6:52 AM, John Jacobsen > > > wrote: > >> After some prototyping and development, we are now getting to the stage >> where "lein run" and a Jetty server running from -main aren't going to cut >> it. >

Re: Current state of the art in Web deployment?

2013-08-18 Thread James Henderson
Hi John, Building on Ray's answer to use Upstart, I've recently started using a Git-based deployment method that essentially uses a Git post-receive hook to re-deploy the application with a simple git push. To set-up, create a bare repo and a working tree on the deploy host, and the relevant U

Re: Current state of the art in Web deployment?

2013-08-18 Thread Ray Miller
On 18 August 2013 17:21, John Jacobsen wrote: > On Aug 17, 2013, at 4:52 PM, Ray Miller wrote: > >> One option is simply to write an upstart script that invokes 'lein >> ring server-headless' and sit an apache or nginx proxy in front of it. >> That's how my website is currently running. Alternat

Re: Current state of the art in Web deployment?

2013-08-18 Thread Sean Corfield
On Sun, Aug 18, 2013 at 9:21 AM, John Jacobsen wrote: > My main concern was just the need to ssh into the server and run leiningen in > the background, as opposed to setting up a "real" server which starts at boot > time. I'm OK w/ wrapping 'lein ring server-headless' with Apache/Nginx, if > t

Re: Current state of the art in Web deployment?

2013-08-18 Thread Steven Degutis
I don't think there is a such thing as a "real" server. Any process that listens on a TCP port and talks HTTP is a legitimate server, regardless of when or how it's started up. Upstart is a fine way to run your server and make sure it's restarted if it dies. It's not hacky or unconventional, in fa

Re: Current state of the art in Web deployment?

2013-08-18 Thread John Jacobsen
Many thanks to everyone who replied about deploying a Web server to production. Specific replies: On Aug 17, 2013, at 6:51 PM, Mark Mandel wrote: > > On Sun, Aug 18, 2013 at 6:52 AM, John Jacobsen wrote: >> After some prototyping and development, we are now getting to the stage >> where "le

Re: Current state of the art in Web deployment?

2013-08-18 Thread Norman Richards
On Sat, Aug 17, 2013 at 3:52 PM, John Jacobsen wrote: > So, what do all y'all do? What is a good lightweight but robust way to > get a fairly simple Compojure/Ring app backed by Datomic facing the outside > world? Not too worried about massive scalability at this point; simplicity > will be a pl

Re: Current state of the art in Web deployment?

2013-08-17 Thread Mark Mandel
On Sun, Aug 18, 2013 at 6:52 AM, John Jacobsen wrote: > After some prototyping and development, we are now getting to the stage > where "lein run" and a Jetty server running from -main aren't going to cut > it. At the risk of asking a dumb question, but being quite new to Clojure, I don't mind -

Re: Current state of the art in Web deployment?

2013-08-17 Thread Ray Miller
On 17 August 2013 21:52, John Jacobsen wrote: > > So, what do all y'all do? What is a good lightweight but robust way to get > a fairly simple Compojure/Ring app backed by Datomic facing the outside > world? Not too worried about massive scalability at this point; simplicity > will be a plus (am

Current state of the art in Web deployment?

2013-08-17 Thread John Jacobsen
Hi folks, I'm starting work on a Clojure Web app and would like to get a sense for the current "standard" (if any) for deploying to production. In my case, I have an AWS Ubuntu instance, set up via Vagrant and Puppet, which mirrors some developer VMs. Datomic, leiningen etc. are running every