This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-07
Channels
- # aleph (11)
- # aws (8)
- # bangalore-clj (4)
- # beginners (32)
- # boot (48)
- # cider (2)
- # cljs-dev (57)
- # cljsrn (4)
- # clojars (22)
- # clojure (67)
- # clojure-argentina (2)
- # clojure-austin (9)
- # clojure-berlin (1)
- # clojure-brasil (15)
- # clojure-france (1)
- # clojure-italy (10)
- # clojure-russia (23)
- # clojure-spec (6)
- # clojure-uk (48)
- # clojurescript (143)
- # cursive (15)
- # datomic (30)
- # emacs (18)
- # hoplon (26)
- # instaparse (1)
- # leiningen (1)
- # om (21)
- # om-next (9)
- # parinfer (3)
- # pedestal (3)
- # planck (2)
- # re-frame (53)
- # reagent (4)
- # ring (5)
- # spacemacs (1)
- # specter (10)
- # sql (16)
- # untangled (19)
- # vim (11)
- # yada (2)
I have a a compojure app that is being deployed to a jetty server running on a linode as an uberwar. I’m using @weavejester environ library to specify database & mandrill configuration etc.. what I can’t work out is how to specify the configuration in the production environment. I’m not running java myself to specify environment variables on a command line. Jetty seems to handle war’s automatically. I don’t seem to be able to turn up anything relevant via Google which is puzzling me. Is this an unusual way to deploy an app?
I don’t really like using environ, it has some hiccups for beginners. One of these is that it doesn’t really offer a clear way to have prod/dev/test environment variables.
But if you still want to go with environ, what I’ve done in the past is that in production I normally use environment variables.
The caveat is that these variables are all strings, while you might have used non-string sin your eviron file during dev. So it might break some things if you don’t parse the strings in your code.
@sandbags: environ isn’t a configuration library. It’s a library for pulling data from the environment. If your production app doesn’t use environment variables, then environ isn’t the tool you need.