I recall seeing that from a while ago - weren’t they planning on rewriting 
emacs effectively?
> On 1 Jun 2015, at 15:55, Mikhail Malchevskiy <malch...@gmail.com> wrote:
> 
> https://github.com/syl20bnr/spacemacs =)
> 
> понедельник, 1 июня 2015 г., 17:05:35 UTC+3 пользователь Colin Yates написал:
> Hi Karsten, 
> 
> Unfortunately our clients are primarily windows based and the software is 
> commercial. tmux - that takes me back! I have never forgotten the joy, or 
> found an equivalent on KDE, Gnome, Windows or OSX of a well configured 
> xMonad, I remember reaching for tmux as a substitute when running over ssh … 
> Sigh - those were the days.  (all we need now is someone to point out the 
> obvious superiority of emacs over vim for this to ignite into a flame war… oh 
> wait…) 
> 
> > On 1 Jun 2015, at 15:00, Karsten Schmidt <in...@toxi.co.uk <javascript:>> 
> > wrote: 
> > 
> > For smaller deployments, so far I've always had a smooth ride using 
> > nginx as reverse proxy and running the uberjar inside tmux. No other 
> > special sauce needed, plus you get the benefit of using nginx to serve 
> > your static assets (if there're not on a CDN already)... 
> > 
> > On 1 June 2015 at 14:40, Colin Yates <colin...@gmail.com <javascript:>> 
> > wrote: 
> >> Thanks Daniel, I am trying to reduce the required installed software on 
> >> the 
> >> client and they can’t access a maven repo from which to download 
> >> unfortunately. Hence I am looking for a ‘self contained executable’ 
> >> solution. 
> >> 
> >> You are yet-another-exclaimer of Boot; enough people have sung its praises 
> >> to make it one of the next things I will need to investigate ;). 
> >> 
> >> 
> >> On 1 Jun 2015, at 14:30, Daniel Szmulewicz <daniel.s...@gmail.com 
> >> <javascript:>> 
> >> wrote: 
> >> 
> >> Great conversation starter. 
> >> 
> >> Many of us had to take down that route. Eventually, we settle on a 
> >> deployment solution that works for us, and we can move on with dev'ing. 
> >> I'm 
> >> sure all the answers are worthy. Please allow me to share my solution to 
> >> this problem. It may not work for everyone, but it works for me. 
> >> 
> >> It can be summarized as follow: Runit supervisor + Boot. 
> >> 
> >> More information here: 
> >> 
> >> https://github.com/danielsz/boot-runit 
> >> <https://github.com/danielsz/boot-runit> 
> >> 
> >> Note: this is the solution I came up with after experimenting with the 
> >> strategies outlined in Ryan's blog post. 
> >> http://www.rkn.io/2014/02/06/clojure-cookbook-daemons/ 
> >> <http://www.rkn.io/2014/02/06/clojure-cookbook-daemons/> 
> >> 
> >> Now I do 'boot dev' locally and 'boot prod' on the server (with auxiliary 
> >> 'boot dev-run' and 'boot prod-run'). 
> >> 
> >> Runit is a Unix classic (as in "an outstanding example of a particular 
> >> style"), and Boot is quickly becoming a Clojure classic. 
> >> 
> >> More examples here: 
> >> https://github.com/danielsz/system/blob/master/examples/boot/build.boot 
> >> <https://github.com/danielsz/system/blob/master/examples/boot/build.boot> 
> >> 
> >> 
> >> On Tuesday, May 26, 2015 at 2:38:30 PM UTC+3, Colin Yates wrote: 
> >>> 
> >>> Hi, 
> >>> 
> >>> I am venturing into new territory using http-kit, as I usually use a 
> >>> 'managed' web server container like tomcat and have a few questions about 
> >>> packing and running a JAR file: 
> >>> 
> >>> - are there are convenient service wrappers for windows and/or Linux 
> >>> - any best practice around managing class path for things like 
> >>> logback.xml 
> >>> 
> >>> I have a jar created from lein uberjar and java -jar the.jar works, but 
> >>> this seems a long way away from automated deployment :). 
> >>> 
> >>> Any advice welcome - thanks! 
> >> 
> >> 
> >> -- 
> >> You received this message because you are subscribed to the Google 
> >> Groups "Clojure" group. 
> >> To post to this group, send email to clo...@googlegroups.com <javascript:> 
> >> Note that posts from new members are moderated - please be patient with 
> >> your 
> >> first post. 
> >> To unsubscribe from this group, send email to 
> >> clojure+u...@googlegroups.com <javascript:> 
> >> For more options, visit this group at 
> >> http://groups.google.com/group/clojure?hl=en 
> >> <http://groups.google.com/group/clojure?hl=en> 
> >> --- 
> >> You received this message because you are subscribed to the Google Groups 
> >> "Clojure" group. 
> >> To unsubscribe from this group and stop receiving emails from it, send an 
> >> email to clojure+u...@googlegroups.com <javascript:>. 
> >> For more options, visit https://groups.google.com/d/optout 
> >> <https://groups.google.com/d/optout>. 
> >> 
> >> 
> >> -- 
> >> You received this message because you are subscribed to the Google 
> >> Groups "Clojure" group. 
> >> To post to this group, send email to clo...@googlegroups.com <javascript:> 
> >> Note that posts from new members are moderated - please be patient with 
> >> your 
> >> first post. 
> >> To unsubscribe from this group, send email to 
> >> clojure+u...@googlegroups.com <javascript:> 
> >> For more options, visit this group at 
> >> http://groups.google.com/group/clojure?hl=en 
> >> <http://groups.google.com/group/clojure?hl=en> 
> >> --- 
> >> You received this message because you are subscribed to the Google Groups 
> >> "Clojure" group. 
> >> To unsubscribe from this group and stop receiving emails from it, send an 
> >> email to clojure+u...@googlegroups.com <javascript:>. 
> >> For more options, visit https://groups.google.com/d/optout 
> >> <https://groups.google.com/d/optout>. 
> > 
> > 
> > 
> > -- 
> > Karsten Schmidt 
> > http://postspectacular.com <http://postspectacular.com/> | http://thi.ng 
> > <http://thi.ng/> | http://toxiclibs.org <http://toxiclibs.org/> 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "Clojure" group. 
> > To post to this group, send email to clo...@googlegroups.com <javascript:> 
> > Note that posts from new members are moderated - please be patient with 
> > your first post. 
> > To unsubscribe from this group, send email to 
> > clojure+u...@googlegroups.com <javascript:> 
> > For more options, visit this group at 
> > http://groups.google.com/group/clojure?hl=en 
> > <http://groups.google.com/group/clojure?hl=en> 
> > --- 
> > You received this message because you are subscribed to the Google Groups 
> > "Clojure" group. 
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to clojure+u...@googlegroups.com <javascript:>. 
> > For more options, visit https://groups.google.com/d/optout 
> > <https://groups.google.com/d/optout>. 
> 
> 
> -- 
> 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
> Note that posts from new members are moderated - please be patient with your 
> first post.
> 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 
> <http://groups.google.com/group/clojure?hl=en>
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to clojure+unsubscr...@googlegroups.com 
> <mailto:clojure+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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
Note that posts from new members are moderated - please be patient with your 
first post.
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
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to