Does anyone know how to get trapperkeeper working with boot?

Nevermind. Got it.

(require 'puppetlabs.trapperkeeper.main)

(deftask run-trapperkeeper []
  (with-pass-thru _
		  (puppetlabs.trapperkeeper.main/-main
		   "--config" "dev-resources/config.conf"
		   "--bootstrap-config" "dev-resources/bootstrap.cfg")))

Do you guys have any opinion on this pomegranate thing I found? https://github.com/cemerick/pomegranate/pull/80#issuecomment-278858505

For boot-cljs-repl , when you (start-repl) , how do you instrument your index.html to connect back to the dynamically generated ws port?

boot.user> (start-repl)
<< started Weasel server on ws://127.0.0.1:55652 >>
<< waiting for client to connect ... 

… I see how to do it if you want to hard-code the port 9001, for example.

But I’m interested in how to do it for the dynamic ports that weasel throws up.

@twashing : my understanding is that you have to run two repls, "boot repl <-- this one you run (serve ... ), and (cljs-repl) , and (watch)" ; then in a seprate shell, you run "boot repl -c // (start-repl)" -- then by some magic, the second one (which I start after the first one), pulls all the port info from the first one

I don't know how they communicate (file?) but somehow they do

@qqq Hmm. Ok. I’m digging into it as we speak.

@twashing : you seem like someone who's not afraid of hardwork; let me grab you the uber docs

Lol. Thanks.. I think :)

https://github.com/magomimmo/modern-cljs/tree/master/doc/second-edition <- someone recommended this to me. I worked through the first 6 tutorials (they're very short).

Ohh

It walks you step by step on how to setup cljs with boot. It's amazing in that it goes "this is the dumb way to do it ;; this become tedious ;; now I will teach you a new feature to make past work trivial "

and at the end of it, you get a very very good understanding of what each of the boot tasks means

boot/cljs did NOT make sense to me until I worked through the first 6 of that series; and afterwards, I got not only a fully working setup, but also a fundamental understanding

I can't oversell / over recommend this.

I’m actually trying to get this working in boot… in trapperkeeper

There’s already an nrepl service in there: https://github.com/puppetlabs/trapperkeeper/blob/master/documentation/Built-in-nREPL-Service.md

I want to see if I can stitch a cljs browser repl in there

I have TK and boot-cljs-repl running separately

Now it’s a matter of making them work together.

can you get cljs browser repl working without trapper keeper ?

Yes

Well… I need to serve up the index.html that connects back to the ws

you know what this means? I can't help you 🙂 because you no longer have a boot problem, you have a trapper keeper problem 🙂

But you get the idea

.

Lol!!

I don't understand how "long running services" and cljs brepl work together.

Well, I think I have a weael problem

when I wnat code reloading, it's because I'm developing locally

if I want long running services, they're on some remote server

I need to know how its generating it dynamic port

Wrt TK...

wait wit wait

I find when I deploy things, it’s nice to have a service that fires up my code and just runs there.

run "cat .nrepl-port"

I thikn that's how the "two boots" communicate the port#

Ahh, that may be it. Lemme check.

yeah, so if you fire up a regular nrepl in boot, it appears it writes a ./.nrepl-port ; which I thikn is how the other nrepl picks it up

That sounds right.

But now, weasel opens a ws on a dynamic port. What I think I’ll do is just spell it out explicitly (cljs-repl 9001).

https://github.com/adzerk-oss/boot-cljs-repl/blob/master/src/adzerk/boot_cljs_repl.clj#L191

Then I can just connect to it, from my index.html: https://github.com/tomjakubowski/weasel/blob/master/weasel-example/src/weasel_example/example.cljs#L6

1) I was right, you're definitely hard working. 2) looks like we have returned to your exact solution from an hour ago -- hard coding 9001 🙂

Hi there. I was hoping I could get some guidance when developing using boot for front end (less, cljs), while the backend is running on vagrant. I'd like to run boot locally, and mirror output to another folder which is served from vagrant.. but I think I lose reloading then?

the backend is not clojure, unfortunately.

I would just rsync the source directory to vagrant

this would cause the vagrant to recompile + reload

watch rsync: local/src to vagrant/src edit: local/src on save, rsync auto runs, updating vagrant/src this triggers cljs recompile + reload on vagrant

@minikomi In addition to http server serving the files, for reloading browser needs connection to http server set up by boot-reload. You could configure boot-reload to use address and port that are accessible from vagrant.

If I was running boot on the vagrant maching I'd do so, but I'd rather have boot running locally than in the constrained vagrant machine. Also, I won't be using clojure in produciton and I'd like to keep my vagrant machine as close to prod as possible

Yeah, it seems like running boot on the vagrant machine simplifies everything. oh well.

So (1) you're running boot locally (2) you want your browser pointed at VAGRANT, not LOCAL, and (3) you want browser to auto reload?

right. when using gulp i was able to do it since every save compiled and output a file to disk - mirrored and served from vagrant.. but the livereload chrome plugin was notified by local server and reloaded the javascript from there.

I think the problem is that boot reload sets up some magic via websockets.

right

So unless your ssh portforward the local ws server to vagrant, it's not clear how it would work.

Actually, there's probably a way to get boot to hardcode the ip address of the ws server, this would cause the browser to load webpage from VAGRANT, but then connect to local for ws.

That would be ideal.

I faced this exact problem.

I thikn the line you want is:

(I should ask for a financial donation here) 🙂

[I'm kidding]

https://github.com/adzerk-oss/boot-reload/blob/master/src/adzerk/boot_reload/server.clj#L64-L66

looks like i can set IP/port? hmm

the line you want is: (cljs-repl :ip (.getHostAddress (java.net.InetAddress/getLocalHost)))

oh wait, maybe this is not what you want; this is for connecting repl ws

you want reload

yeah, i think reload should work just fine

it's more, the output js / less -- should I do a sift to make it output after every watch?

i'm still a bit unsure how boot-cljs, boot-less and boot-http work without outputting to a build folder

some kind of tmp folder magic?

fileset contents are available from classpath

I have never used boot-less, so this unfortunately is the limit of my helpfulness.

but I think (1) if you just rsync, live.js will pick it up and (2) if you have websockets pointed at correct ip, brepl should work -- and it's not clear you need anything more

local files from my backend folder are automatically mirrored to the vagrant machine

i'd ideally like to get output from less/cljs into a /static folder there

isnt't this just watch + rsync, or is there something more ?

sure.. I guess I'm not sure where files are being output when I don't do a sift/target? Or, should I do that in my dev build too to get the files?

(defmulti foo :foo)

Not entirely sure how to go forward from here.. can you give me another hint? 🙂

@qqq The following worked fine for me:

cljs.user> (defmulti foo :foo)
nil
cljs.user> (defmethod foo 1 [] "one")
#object[cljs.core.MultiFn]
cljs.user> (foo {:foo 1})
"one"

@minikomi: thanks! that worked for me too. For some weird reason, the difference is: 1. if I type it in the repl buffer, it works 2. if I type it in my source buffer and do eval-last-sexp, it fails this is very helpful as it points the bug at "what is the difference between typing in repl vs C-x C-e"

@minikomi : thanks! that fixed my problem

are you still stuck on your problem?

I think just using a (target) at the end if my dev pipeline solves what i want

yeah, (target) is what causes stuff ot be written out

how would it be possible to work without a target?

using (serve) was working for just local files

:ws-host was what i wanted for reload.. works great!!

Enjoyed reading https://adzerk.com/blog/2017/02/faster-clojure-metadevelopment-with-boot/, thanks @alandipert

the poll function looks like a great hack

exactly the kind of idea you're inspired to when working from a repl

@pesterhazy thanks man, that was exactly my goal, spark the imagination

this is amazing. I usually don’t write many boot files so that wasn’t a big problem for me to wait 7 seconds. But for demos when you show how to use create boot files (or perun tasks in my case) this is great

@pesterhazy @alandipert pool should be a builtin, I have used (load-file "build.boot") so often that I ask myself "why can't boot just reload this too)

any advice to speed up uberjar creation?

on our ci server the uberjar creation part of the build takes over 10 minutes

@hiredman Are you making sure dev/test-only source and dependencies are excluded?

yes

@hiredman I think @micha mentioned something about a function which could cache library explosions for uberjars. I'm not sure if it was used in the latest boot or not though.

yes uberjar explosion is cached

in theory that should work fine, unless there are bugs

@hiredman are you all up to date?

well a cache only works if your build carries the cache forward between runs

the build should use .boot for storing stuff

is there some project that generates nice html docs for boot tasks?

not that I know of

@alandipert Awesome post.

@podviaznikov You could try with codox.

Not specific to Boot tasks, mind you.