@richiardiandrea: is there some more documentation about boot.parallel? Definitely add it to the changelog 🙂

with 2.6.0, if I want to point Boot to my Clojars mirror, do I have to do it through the env variable? Should I do it through the :repositories key?

you don't need to use the env var unless you want to affect how boot loads its own dependencies, before your build.boot/profile.boot are read

ok, I see

thx

@martinklepsch: well there are docstrings :) I agree it is a bit of an esoteric feature ahah

@alandipert: thinking of doing something similar?

na just thought it was neat. free library idea 😄

sbt?????

@richiardiandrea: http://www.scala-sbt.org/

ah ah yeah I know what it is 😄

@anmonteiro: have you tried lambone yet?

I haven't

I’ve put that aside for now

kk

play time is over

maybe on the weekend 🙂

ok cool, yesterday while playing I added Dirac, optionally, of course for people who don't want to use cljs-repl...

@richiardiandrea: I could not get refresh to work though

I mean, I could if I called it directly in boot.user

yes for that I have two repls running (same JVM)

not cider-refresh, though

and that’s something which works out of the box with Lein

it looks like tools.namespace does not play well with something (I could not understand what)

I didn’t have more time to explore it as well

no but it does work, if you exclude frontend tasks

i mean cljs tasks

I see

that is why, one of my repl only has "clj" tasks and in there I am able to refresh no problem

exposing the api on port 3000

the other part serves static content on port 8000 (and another cljs repl, with boot-reload)

@richiardiandrea: https://github.com/Deraen/boot-ctn should setup c.t.n watch dirs correctly for Boot

Not sure if it works with Cider

^: @anmonteiro

@juhoteperi: that's weird because it works for some tasks and not for other, but I will try it out

@richiardiandrea: Tasks that use c.t.n inside pods need to set the watch dirs themselves

ah that's why

Thx, I’ll keep that in mind

basically my clj pipeline only has the repl task in a pod

that is why is working there

Also, I could not get 0.2.x working inside pods myself, but I was able to use 0.3 alpha, with low-level API (track and reload instead of repl), check boot-alt-test for this

I definitely will

tnx

@juhoteperi: if you use (:directories boot.pod/env) instead of (boot.core/get-env :directories) your code will work in any pod

@micha: Yes, but tasks need to set the dirs again inside the pod because setting the dirs in "root pod" doesn't affect new pods (I think)

right because they'll have separate instances of the c.t.n namespaces

isolated, different vars

right

And with the low-level API, that tasks probably should use, the dirs should anyways be provided as parameter to scan-dirs: https://github.com/metosin/boot-alt-test/blob/master/src/metosin/boot_alt_test/impl.clj#L45-47