This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-02
Channels
- # aleph (3)
- # announcements (2)
- # babashka (4)
- # beginners (74)
- # calva (21)
- # clj-kondo (30)
- # cljs-dev (7)
- # cljsrn (42)
- # clojure (121)
- # clojure-dev (13)
- # clojure-europe (23)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-norway (7)
- # clojure-spec (140)
- # clojure-uk (58)
- # clojuredesign-podcast (9)
- # clojurescript (49)
- # clojutre (2)
- # cursive (32)
- # datascript (2)
- # datomic (59)
- # duct (7)
- # figwheel-main (6)
- # fulcro (18)
- # graphql (5)
- # jackdaw (1)
- # joker (6)
- # juxt (7)
- # leiningen (9)
- # off-topic (1)
- # pedestal (14)
- # quil (2)
- # re-frame (3)
- # reitit (8)
- # shadow-cljs (78)
- # sql (8)
- # timbre (3)
- # vim (69)
I'm trying to migrate a project to aero, that's currently using just lein-environ
if I just change all the calls to (environ/env :something)
to use a config value like #env SOMETHING
it doesn't work, because the env variables are defined in project.clj
so they are not actually returned by System/getenv, which is used by aero internally
I can still of course get it done, but to make the migration more seamless, it would be great if I could pass a different env
function
Ideally something like that it's only temporary anyway, but maybe it could be useful for others as well?
I don't know about lein-environ but you could alsodefine your own tag, like 'myenv' and use '#myenv' in your config file instead
Ah cool I could try that thanks