Fork me on GitHub

Hi everybody, I'm announcing Boot tasks to get certificates from Letsencrypt.


One recent talk at Clojure Conj was saying that Java is Clojure's assembly code. Can't be bad ๐Ÿ˜€๐Ÿ˜€


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?


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.


You'd have to work around it, but it's not the easiest thing in the world and I don't remember enough to tell you exactly what to do. The gist is that the pod's streams need to be handled separately


well, one side of the problem, I guess