What do you do when a boot task plugin you depend on doesn’t run because of an older dependency? Can you override it somehow within your build.boot file?

you can do boot show -p

Ok, I’ve already pinpointed it down

Sorry, was distracted when I wrote that. I know it’s from an older version of httpkit used by boot-livereload

you can do those commands in a pod also if you need to

like to debug deps in a pod

Is there an example of how to customize tasks or pipelines between dev and production env?

@jayzawrotny you can do like

boot -e foo=bar repl

and then in the repl

boot.user=> (get-env :foo)
"bar"

you can use this perhaps, like boot -e environment=production task1 task2 ...

a cleaner way might be to use an environment variable

like you'd set that environment variable in your CI configuration or whatever

and you'd look for it in your task

(if (= (System/getenv "ENVIRONMENT") "production") ...)

The environment var makes a lot of sense. Thanks! I am still curious what a task implementation that responds to the env var would look like. Especially one that relies on composing a bunch of tasks together.

(deftask foo
  []
  (comp 
    (case (get-env :foo) 
      "bar" (task1) 
      "baz" (task2) 
      (task3)) 
    (task4)))

something like that?

you can do anything in there of course

I see. That’s why no concrete examples are in the documentation 🙂 Thanks again.

yeah i looked in the wiki and didn't see anything

FYI, boot-clj + rebl https://gist.github.com/jeroenvandijk/a7f802bb9105bdc617b475d5996ba86b