This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-05
Channels
- # adventofcode (419)
- # aleph (8)
- # aws (6)
- # beginners (148)
- # boot (9)
- # cider (24)
- # cljs-dev (37)
- # cljsjs (8)
- # clojure (134)
- # clojure-android (6)
- # clojure-brasil (15)
- # clojure-dev (8)
- # clojure-dusseldorf (2)
- # clojure-greece (67)
- # clojure-italy (8)
- # clojure-japan (3)
- # clojure-russia (3)
- # clojure-spec (8)
- # clojure-uk (13)
- # clojurescript (54)
- # clojurex (6)
- # cursive (5)
- # data-science (12)
- # datomic (15)
- # defnpodcast (11)
- # emacs (25)
- # fulcro (95)
- # graphql (3)
- # lein-figwheel (1)
- # leiningen (27)
- # luminus (1)
- # lumo (6)
- # mount (2)
- # off-topic (112)
- # om (3)
- # onyx (24)
- # perun (3)
- # re-frame (20)
- # reagent (1)
- # reitit (2)
- # ring-swagger (13)
- # rum (10)
- # shadow-cljs (45)
- # spacemacs (24)
- # sql (2)
- # unrepl (78)
- # yada (1)
if anyone's interested I started gorilla repl from boot today, just to have the choice to use boot if wanting to https://gist.github.com/elisehuard/f7f488693e379bca66669c613d0bddb3
it was moderately painful, turns out boot can be a bit unfriendly
@elise_huard you are the true hero
@hswick shouldn't be too difficult, I'll have a look on how to do that
I'm not too happy with the stop though - gorilla-repl stops when receiving SIGINT (ctrl-c)
it works on the linux shell command line (boot gorilla) but when starting from the repl (boot (gorilla)) it happily runs on in the background until you kill the repl
(on the linux command line the parent process just dies which takes care of things)
hmmm, i might suggest that gorilla be its own process and the repl just sends messages to it
We built and have used this successfully: https://github.com/Provisdom/boot-gorilla