#hoplon

awesome!

yeah that's what i am aiming for

it's really hard to keep up with all these projects

last i ran it (it takes a while to get going, github throttles hard) it was at 144 projects

that was a couple days ago

whoa!

that's a lot

yeah nice!

in addition to monitoring that, i want that repo to serve as an illustration of boot's power with some fairly customized deployment strategy

so i want to stick the frontend on github pages and the backend on heroku

hence the boot buildpack i made for heroku

oh that's great

so you can push to heroku and it knows how to bootify it?

yeah, i'll keep chipping away at that, would be cool to have i think

yeah

even caches .m2

awesome

heroku is really good for new people

yeah, easy, free

like you can show someone something and they can push it to heroku to deploy immediately

ha so the funniest part of this app is how i am trying to deal with persistence

since heroku gives you no guarantees with regard to disk

so i am just modeling the data as sets and storing it distributed across everyone's browser's localStorage

ghetto bittorrent

i love it

yes!

lol

the free heroku redis is like 5MB of storage, i thought naahhhh we can do something ghetto fabulous

pandeiro: How is boot-test-cljs coming? It's the only thing missing from my dev workflow with boot ;)

DomKM: eeeesh :-/

I ran into a blocking issue with that

pandeiro: heh, no pressure ;)

I could really use it though, as well

DomKM: I'm sure you know there are alternate ways of compiling and running tests, I can recommend another strategy for the time being

I would also *love* another pair of eyes if you feel like debugging that with me: the issue is basically that previous builds were affecting the current build's compiler output -- why, I could not figure out.

pandeiro: I'm just using serve and reload to run them in a browser, for now. Is this how others are running cljs tests or is there a better way?

DomKM: that's a great way IMO

i usually have a tests.html specifically for that

and you can swap the favicon out when tests fail/pass if you want to get fancy :)

heh

boot-test-cljs's intent was for testing for things like library development where browser is just a distraction... i'll eventually get back to it

Unfortunately, this is for a library that doesn't require serve otherwise, which is why boot-test-cljs is appealing :)

ha, yeah...

pandeiro: bootcamp is awesome… I'm checking it out now

is the boot clj working on windows? Do I need to install some sort of dependencies ?

gzmaska: you downloaded boot.exe?

yup, and copied it into system32 too

and now in the windows command

and boot build gives "Illegal character in path at index 2: ..\"

you should be able to type boot and see something

that looks like a bug

yeah, I was able to get the help text up and get the deps installed somewhere under my User's folder

so I guess it's not ready for prime time on windows then ...

probably not

assistance welcome for windows

I might be able to help. Where is the code the handle windows directories?

it's in the stack trace, which you can get if you do `boot -vv build`

the -vv puts boot in extra-verbose mode

which will emit full stack traces

looks like the illegal char error happened @ boot.file$relative_to.invoke(file.clj:80)

gzmaska: there was a fix for that in the master branch

if you can build boot from master and test that would be awesome

I see, do I use launch4j to build the project?

yep

if it's available on your system the makefile will handle it

do you have gnu make installed?

or some kind of make command anyway

not on my working PC but I could set the building environment up here

i'm thinking about moving to appveyor.com for CI stuff

it has a windows build environment

what are you currently using?

drone.io

linux only

bsima: it's a mess currently but thanks! please go wild and send PRs if you're inclined

piranha: any luck with whidbey integration?

raywillig: well, middleware is easy to enable, but then I didn't have much time with clojure, so no ideas about all those :nrepl-context things

http://paste.in.ua/10325/ - that's my .profile.boot

i was looking at that in plugin.clj. seems like that's something specific to how lein does it. does that gist work for you?

piranha: does that setup auto pretty print in color for you?

raywillig: yep

hm, not exactly

everything's blue :)

i put this into my build.boot on a project i'm working on and if i examine boot.repl/*default-dependencies* and *default-middleware* i see the deps etc but it doesn't affect my output

exceptions are red

yeah, not exactly colored

i was getting blue before i did that lol

maybe necessary to set puget options somehow

yeah...

i think that's what he's doing with alter-var-root in the :injections section of the plugin code

raywillig: https://github.com/greglook/whidbey/blob/master... I suppose that's the problem

not puget options, but something for nrepl interative-eval

no idea what this :nrepl-context does, I can't find it referenced anywhere

puget-options by default contain {:print-color true}, which seems good enough

oh true, when i invoke puget manually in the repl i get nice output with any mods

without any mods

this :interactive-eval should be passed somewhere to nrepl

but I really have no idea where

i'm also completely lost

I wonder if that's some option to nrepl

and we should be looking for it there - just because lein passes :repl-options to nrepl without looking at them

hey!

raywillig: I found it!