Re: lispy ways of handling dev mode

2010-10-04 Thread Michael Ossareh
On Sat, Oct 2, 2010 at 22:46, Scott Jaderholm wrote: > On Sat, Oct 2, 2010 at 6:36 PM, Michael Ossareh wrote: > >> What is the recommended manner in which to let your application know its >> on a dev machine? >> > > I use an environment variable that determines which config (dev, > production, t

Re: lispy ways of handling dev mode

2010-10-02 Thread Scott Jaderholm
On Sat, Oct 2, 2010 at 6:36 PM, Michael Ossareh wrote: > What is the recommended manner in which to let your application know its on > a dev machine? > I use an environment variable that determines which config (dev, production, test) gets loaded. APPNAME_CONFIG=development lein swank I don't

Re: lispy ways of handling dev mode

2010-10-02 Thread Phil Hagelberg
On Sat, Oct 2, 2010 at 3:36 PM, Michael Ossareh wrote: > In java I'd normally have a conf file somewhere, and that had a range of > issues so I'm wondering if there is something more lispy Actually it works really well to use the classpath. Leiningen (and presumably other tools) will place test/

lispy ways of handling dev mode

2010-10-02 Thread Michael Ossareh
What is the recommended manner in which to let your application know its on a dev machine? I'm building an app that sends emails based on certain events, however when I'm developing locally I'd rather it print the email to my log file. I have a variable in that namespace: *send* which is def'ed to