This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-31
Channels
- # aleph (3)
- # aws (5)
- # beginners (65)
- # boot (17)
- # cljs-dev (112)
- # cljsrn (5)
- # clojure (146)
- # clojure-austin (3)
- # clojure-dusseldorf (3)
- # clojure-italy (18)
- # clojure-norway (13)
- # clojure-russia (84)
- # clojure-serbia (5)
- # clojure-spec (24)
- # clojure-uk (84)
- # clojurescript (204)
- # css (1)
- # cursive (21)
- # data-science (3)
- # datascript (21)
- # datomic (26)
- # emacs (5)
- # euroclojure (1)
- # hoplon (8)
- # jobs (7)
- # jobs-discuss (2)
- # keechma (35)
- # lumo (92)
- # mount (1)
- # nrepl (2)
- # numerical-computing (16)
- # off-topic (10)
- # om (58)
- # re-frame (13)
- # reagent (90)
- # remote-jobs (2)
- # ring-swagger (1)
- # spacemacs (9)
- # specter (6)
- # unrepl (17)
- # untangled (56)
- # yada (2)
Hi everybody, I'm announcing Boot tasks to get certificates from Letsencrypt. https://github.com/danielsz/certificaat#boot
Very nice!
One recent talk at Clojure Conj was saying that Java is Clojure's assembly code. Can't be bad ๐๐
Is anyone else having this issue? https://github.com/boot-clj/boot/issues/585
I haven't double checked now but it used to be a problem yes โ๏ธ
anyone using boot-http/serve can tell me, is there a problem with logging things onto stdout? it seems because it lives in a different pod this might be a bit problematic (?) or itโs me doing something wrong?
anyone been using this or a similar workaround? https://github.com/adzerk-oss/boot-cljs-repl/pull/40
I've never had a problem adding eg a simple println
to a handler and seeing the output
pandeiro: yeah, it seems some middleware, doing something strange. I moved a handler to the top of the chain, and it prints
@richiardiandrea I'm asking because it doesn't happen to me anymore, unless I'm trying something wrong
@donyorm I'll verify that too in a while
@ag yeah, pods and input/output streams interact a little weirdly. I don't remember all the specifics, but in pods, System/in
and System/out
aren't connected to the main pod's *in*
and *out*
. If you remember the controversial cider bug that I fixed, this was the basic problem. (Edit to add that the same goes for *err*
)
@U051706GF: can that be classified as a bug? Or that's something you have to use some workaround to deal with?
No worries :). For what it's worth, the boot problem is inherent to the nature of pods as isolated clojure runtimes, so I don't think it can be changed.