This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-27
Channels
- # arachne (1)
- # beginners (31)
- # boot (84)
- # cider (9)
- # clara (2)
- # cljs-dev (102)
- # cljsrn (20)
- # clojure (254)
- # clojure-belgium (1)
- # clojure-dusseldorf (17)
- # clojure-greece (7)
- # clojure-italy (6)
- # clojure-russia (2)
- # clojure-spec (8)
- # clojure-uk (9)
- # clojurescript (93)
- # component (4)
- # copenhagen-clojurians (1)
- # cursive (24)
- # datomic (22)
- # editors (1)
- # emacs (8)
- # garden (2)
- # hoplon (357)
- # lein-figwheel (1)
- # leiningen (4)
- # luminus (27)
- # mount (13)
- # off-topic (7)
- # om (71)
- # onyx (35)
- # planck (3)
- # re-frame (53)
- # reagent (35)
- # ring-swagger (24)
- # specter (10)
- # sql (6)
- # untangled (47)
- # vim (157)
@doglooksgood: take a look at these examples: https://github.com/tolitius/stater they are boot based. as far as "continues" testing, I usually do boot watch speak test
in a different REPL and all tests run automatically on changes
(deftask run-tests []
(set-env! :source-paths #(conj % "test/server"))
(mount/start)
(comp (watch)
(speak)
(test)))
I wonder where should I call mount/start
usually you would have calls to (mount/start)
within the tests, so you can just do: https://github.com/tolitius/mount/blob/master/build.boot#L73-L75
where tests would start / stop parts of the app, or the whole app, depending on what needs to be tested: https://github.com/tolitius/mount/blob/master/test/core/mount/test/start_with.cljc#L25-L32
Just to follow up from yesterday (thanks again @dm3 and @tolitius!), it ended up being super simple to use CLI options with cprop & mount.
Here's the -main
fn: https://github.com/pmonks/bot-unfurl/blob/master/src/bot_unfurl/main.clj#L61
And here's where the config file specified on the command line ends up: https://github.com/pmonks/bot-unfurl/blob/master/src/bot_unfurl/config.clj#L21
From there on, it's vanilla mount all the way down!