This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-13
Channels
- # aleph (1)
- # beginners (105)
- # boot (6)
- # cider (9)
- # cljs-dev (61)
- # cljsrn (59)
- # clojure (132)
- # clojure-germany (1)
- # clojure-italy (6)
- # clojure-russia (18)
- # clojure-spec (1)
- # clojure-uk (58)
- # clojurescript (56)
- # core-async (1)
- # cursive (17)
- # datomic (20)
- # docs (1)
- # duct (5)
- # editors (1)
- # emacs (7)
- # events (2)
- # figwheel (7)
- # fulcro (30)
- # graphql (8)
- # jobs (3)
- # leiningen (23)
- # luminus (14)
- # mount (6)
- # off-topic (41)
- # onyx (14)
- # protorepl (2)
- # re-frame (7)
- # reagent (32)
- # shadow-cljs (236)
- # tools-deps (92)
- # unrepl (8)
- # vim (60)
- # yada (1)
@callum what are you trying to achieve by doing that?
Leiningen has the concept of user profiles
but it's not quite the same as npm i -g
because the dependencies are always* used in the context of a project
* you can run a REPL outside of a project, but it's not quite the same
If you add plugins to your lein profiles.clj
(https://github.com/technomancy/leiningen/blob/master/doc/PROFILES.md) then you can run them from anywhere on the system
@danielcompton slightly weird situation… we have a clojure docker image being built which installs leiningen as part of its build. Then an application image which builds on top of the clojure image and pulls down the dependencies. All of this happens under the root
user and the application itself is eventually run under an application
user, it would be great if the dependencies could be available for all users
Is your application run as an uberjar?
I would probably set my local repo to be a shared location that both users can read/write to
@callum more a thing for #docker but once you start pulling in dependencies inside dockers it makes a lot of sense to use a volume for your maven repo, preventing needing to download it multiple times.
it’s looking more and more like we’ll have to spend the time to move away from the docker containers we’ve been provided with
thanks @danielcompton!
@gklijs yeah, that works well for a local dev situation but when it comes to running our app in CI (for tests etc.), we generally pull the deps down during a docker image build and then push that image to a docker repo. we then pull that image down when running docker in CI