Fork me on GitHub

Does keys in :profiles such as :dev, :repl, :cljsbuild means I can use lein dev, lein repl , lein cljsbuild? Why does the lein figwheel dev work? Does lein figwheel dev use :dev profile?


@cmal: you should read this article about profiles:


TL;DR; it is complicated, some profiles are special and are used just based on naming convention, e.g. :repl or :dev, some others are used implicitly by leiningen plugins


when you run lein figwheel dev, the dev there has nothing to do with profiles, it means that figwheel will autostart “dev” build in your :cljsbuild :builds


@cmal I have just tested your project on my machine, I was able to reproduce the problem you are seeing. it is caused by another “automagical” leiningen behaviour, profiles get merged, if keys are maps, they get merged, but if they are something else like list, they get concat, and in some special cases something custom happens, one special case is :repl-options :init, the code there gets wrapped into a (do …) form which lists all forms from merged :repl-options :init in profiles


long story short, delete :repl-options in :dev profile and it will work as expected


@darwin Thank you very much for your help and patient explanations. I will take a note here and then dive into the docs of lein to learn more.


@darwin Hello again, my friend and I have started enjoying Dirac. Thanks. Regarding the Dirac agent, what do you think to change its listening binding from to because (as you know) I am using the docker and the change would make my life easy (:


either set env variable DIRAC_AGENT__NREPL_TUNNEL__HOST, or pass config map to (dirac.agent/boot!) in your project.clj


:agent-host and :agent-port there should match :nrepl-tunnel setting in the agent


Oh great! the setting can be changed with env setting. Thanks I will try that.