This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-12
Channels
- # admin-announcements (1)
- # bangalore-clj (13)
- # beginners (149)
- # boot (123)
- # cider (7)
- # clojure (167)
- # clojure-brasil (3)
- # clojure-greece (1)
- # clojure-korea (2)
- # clojure-new-zealand (2)
- # clojure-russia (70)
- # clojure-sanfrancisco (3)
- # clojure-spec (84)
- # clojure-uk (36)
- # clojurescript (300)
- # code-reviews (242)
- # community-development (34)
- # core-async (4)
- # css (1)
- # cursive (37)
- # datascript (1)
- # datomic (20)
- # defnpodcast (1)
- # dirac (15)
- # events (7)
- # garden (12)
- # hoplon (100)
- # lein-figwheel (11)
- # off-topic (2)
- # om (69)
- # om-next (3)
- # onyx (86)
- # planck (14)
- # proton (4)
- # protorepl (1)
- # quil (2)
- # re-frame (53)
- # rum (3)
- # untangled (1)
- # vim (50)
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?
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
@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 127.0.0.1 to 0.0.0.0? 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
here is how it gets propagated from the boot!
call:
https://github.com/binaryage/dirac/blob/master/src/agent/dirac/agent/impl.clj#L139
@tf0054 you might need to tell the runtime exact ip to connect to: https://github.com/binaryage/dirac/blob/master/src/runtime/dirac/runtime/prefs.cljs#L20