This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-28
Channels
- # announcements (3)
- # babashka (36)
- # beginners (77)
- # boot (3)
- # chlorine-clover (10)
- # cider (27)
- # clj-kondo (1)
- # cljs-dev (4)
- # clojure (256)
- # clojure-belgium (1)
- # clojure-europe (9)
- # clojure-uk (18)
- # clojuredesign-podcast (9)
- # clojurescript (54)
- # cryogen (8)
- # cursive (3)
- # data-science (1)
- # datomic (2)
- # duct (31)
- # events (1)
- # exercism (3)
- # fulcro (116)
- # joker (20)
- # kaocha (5)
- # meander (2)
- # nrepl (4)
- # off-topic (10)
- # other-languages (15)
- # re-frame (18)
- # reagent (4)
- # shadow-cljs (44)
- # sql (14)
- # tools-deps (17)
apologies if this is in the docs, but is there a way to give a path to a deps.edn
, instead of assuming it's in the current working directory?
(I'm coexisting with a bunch of Python and I'd prefer to have one deps.edn someplace else and just use long Makefile
commands to get at the clojure libs)
(or rather, I'll just cd other_place && clojure ...
to keep my Python colleagues from tripping over the clojure stuff).
@rgm One thing you can try is specifying CLJ_CONFIG=/path/to/folder clojure ...
where your deps.edn
file is /path/to/folder/deps.edn
-- this treats that deps.edn
file as the user-level one, ignoring your ~/.clojure/deps.edn
(and it would still pick up a deps.edn
file in the current folder).
(so you'd get system deps, CLJ_CONFIG deps, current/project deps)
We use this approach in our monorepo at work, so we can have a "standard" user-level deps plus our current subproject deps (and ignore any developer-level user deps on different machines).
right, and because it's env, I can just manage it through settings in Makefile
, or .env, or direnv, or ... this is great.