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)

no

drat.

symlinks it is ¯\(ツ)/¯

(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)

oh, that's a great trick ... I don't have a ton of deps

don't really even need a current folder one.

(which is what got me going down this path, to keep things tidy).

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.

(Can I just say you and Alex are killing it, and it’s much appreciated?)

@rgm fwiw deps.clj (an unofficial clj script re-implementation, or the binary version deps.exe) does have an option for this