This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-01
Channels
I believe you control the output directory with :compiler-options {:asset-path "/path/you/want"}
@domkm: things being written to out in your project dir can only be done by output options. I'd check there. Gotta sleep now. Talk later!
@martinklepsch: Output options in that pipeline?
sigh, just to let you know that my supposed deterministic system is being thwarted by logic in boot. I'm getting this error "Please download latest Boot binary:
@domkm: there were no options in your snippet but I guess somewhere in the stuff you trimmed maybe?
@sjm: that should only happen when you updated boot and didn't pin a version in your project.
Okay, I turned on my machine, ran nix-shell
(after running it yesterday) then ran boot dev
the exception threw. I tried changing my nix scripts to point to the new boot_bin
but I got the same error. How exactly do I pin a boot version to my project? On the train atm sorry for the vague response.
@sjm: boot -V prints a thing that you can put into boot.properties
If there's a boot version given there it uses that one.
I think new boot-bin is not yet officially released
Try 2.4.2. Should work with any the latest boot.sh from the boot project or boot-bin
anyone headed to oredev this week? i'll be there tuesday, would love to meet up with boot users
@martinklepsch: ah thanks, I updated the nix scripts to point to the new boot_bin properly. Boot works now.
hey guys, just started using boot - trying to use devcards with it: https://github.com/bhauman/devcards#usage-without-figwheel
where should the build-options go?
eh, i’m halfway there - i got the devcards title to show up, but none of my cards are rendering
@kurtlazarus: @jgdavey shared https://github.com/hashrocket/boot_devcards_example the other day, might be worth checking out
awesome
thank you @alandipert
A boot upgrade can fail in a few ways... 😕 I've Ctrl-C'd it because I thought if I ask it to upgrade, then it would download 2.4.x, but instead any consecutive runs fail with the error shown:
> boot dev
Downloading
> boot -u
Exception in thread "main" java.lang.ClassNotFoundException: boot.App
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
...
i was installing boot with brew install boot-clj
.
i tried to uninstall and install it again, but that doesnt help
we have a fake "latest" branch so you can download from the same url to get the latest thing
there are also real tags and releases in case you want to package it and need a versioned url
@martinklepsch: That's the complete task. I didn't think anything I previously left out would change cljs compilation.
@martinklepsch: btw, the "out/" dir gets created when I connect to the nrepl server and type (start-repl)
to turn it into a cljs repl
Probably a problem with boot-cljs-repl not setting all all the options
@micha: Good sunday afternoon!
@micha: you mentioned you had something you wanted to push?
like something related to the boot builds boot stuff
you mean like deploying to clojars?
@martinklepsch: i added a thing today to let you do boot show ...
on any pod
that sounds great. how do you point to a pod? or does it just print it for all?
how does it work with multiple pods from the same ns?
nice one
like if you are making lots of pods, or if you are making a library that will handle pod creation on behalf of other libraries
caching for what?
when are they dumped from the cache?
how can you make it more pervasive than that?
I don’t think I understand. Isn’t most stuff linking anyways? Things are only copied to the blob store once?
but only ever once when starting the pipeline
are you talking of caching for this startup phase?
ok, makes perfect sense then
@micha: re that deploy issue: you made sure you’re not building the version of boot you’re using?
How did you test the deploy? pushed to some other groupId?
@micha: doesn’t handle things on a per dir basis but I guess that’s an acceptable tradeoffs as dirs don’t change usually..
In Boot, but in theory it’s not impossible right?
but then the set would be different and everything would need to be linked again
ah you mean add the dir to the key
yeah I suppose that would work. Felt more general to just key by dir but I like the size if your diff more
Pull in the tests though
https://github.com/boot-clj/boot/pull/327 — merge this one too maybe?
@micha: wondering if you have thoughts on merge commits vs. rebased fast forward merges? I usually don’t see much utility in merge commits, especially if it’s just single commits.
Alright. Good night!
does anyone have thoughts about what a presentation of boot to non-clj/cljs users should include/not include?
i am presenting this week at a general dev con and the talk introduces the concept of programming with values, then introduces fileset
(in the process of prep i realized how hard a presentation of boot to people who don't know clj will be, am a little scared)