This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (59)
- # announcements (1)
- # beginners (67)
- # boot (140)
- # cljsrn (8)
- # clojure (70)
- # clojure-berlin (18)
- # clojure-dev (7)
- # clojure-russia (53)
- # clojurescript (124)
- # clojurescript-ios (3)
- # clojurewerkz (2)
- # clojurex (10)
- # code-reviews (42)
- # cursive (9)
- # datomic (2)
- # editors-rus (2)
- # emacs (5)
- # events (1)
- # hoplon (35)
- # jobs (8)
- # ldnclj (7)
- # lein-figwheel (34)
- # luminus (1)
- # om (410)
- # onyx (22)
- # overtone (19)
- # portland-or (6)
- # re-frame (1)
- # yada (4)
@juhoteperi: running into the old clj 1.7 instaparse StringReader arity bug with boot-livereload, is this something youve run into?
looks like instaparse is coming in through clj-livereload -> compojure -> clout. i was able to fix by excluding instparse and explicitly dep on instaparse 1.4.1, wondering if i'm missing something
@alandipert: I'd talk about the immutable fileset. Applying an FP concept to something inherently mutable (project building) makes things like task composition easy.
yeah, i think i'm gonna start with that - show off boot -d .. repl and bring up incanter, other flashy libs
btw, have you looked at capsule (http://capsule.io) and the synergies between boot and capsule?
I meant run in the sense of using it as a launcher for deployment, running pods in production
worth mentioning as not everyone will make a connection between running tasks locally and that
what's a good way to communicate between pods, e.g. one pods needs to trigger a restart of the other pod with updated dependencies. Can they somehow communicate via boot.core?
guess I can share an object between pods if its class is loaded in boot's parent classloader
in the same vein: when is it appropriate to create new boot cores, like in https://github.com/micha/multi-module-build/blob/master/build.boot
Though now that I compared them both I think saapas is a bit closer to what I want at the moment, since it has a sample backend as well and I would have to add it to a tenzing generated app by hand
I'm basically playing around with to see how workable would be having a presentation that's also a working application with backend that you can hot reload with system on the backend and boot-reload on the frontend
I wouldn’t take any offence I was just curious if there’s something that’s bugging you/could be improved
Also, I think there was a boot task that created a synchronised
project.clj out of the dependencies in
build.boot, sort of a reverse of
from-lein (https://github.com/boot-clj/boot/wiki/Using-Boot-in-a-Leiningen-Project). Am I making things up or is this a real thing?
https://github.com/boot-clj/boot/wiki/For-Cursive-Users — this might be what you’re looking for?
made this thing today: https://github.com/martinklepsch/custom-comparator-set — would be curious about feedback
you might want to do this when you have multiple modules that depend on each other and aren't really suitable to develop separately
the boot clojure code is factored into like 4 or 5 separate jars so that different pods can be started with different permutations of those loaded
so like if you have builds that need to start in a certain order, like in the multi-module example, you can do it by storing a Semaphore or something in there
and tasks in the different boot instances can all see it and use it to synchronize themselves
do you know of a java concurrency construct that can impose ordering on the execution of async tasks?
i want to be able to ensure that async process 2 doesn't start until async process 1 has done its work
but it seems like this kins of thing could be controlled by an actor which gets events of completion
most of the issues with multi-module builds are solved pretty well by the
but like to build boot itself, which has unusual structure because of the classloader setup
Hello, I have a use case for using boot scripts at work (yay 😛 ) : migrating data from a database to another (mongo -> rethink). I was just wondering, how can I have a REPL to my boot script (ex.
I'm getting a weird error from either simple or advanced compilation: (intermediate value)(intermediate value)(intermediate value)(...) is not a function. You can see it on a running webserver here: https://client.app.takemyspot.ca/
@martinklepsch: you were asking yesterday to see some use case for the boot.pod/data thing
@flyboarder: it just got easier, since there is now a single download url for boot.sh that will never change (or you could even put boot.sh in your git repo, it's only 5k or so)