Fork me on GitHub
#boot
<
2017-11-08
>
mattyulrich03:11:56

Sorry for the delayed response - got tied up at work... @alandipert I've just been using boot as the entrypoint - specifically to use the repl during dev... This is for a testing tool that I'd like to deploy to a few other environments so I can run from boot or uberjar - whichever is easiest... Any thoughts?

seancorfield03:11:26

@mattyulrich I'd recommend you look at either starting a full nREPL server inside your application programmatically, or the socket server feature that was added to Clojure (in 1.8).

seancorfield03:11:17

We used to start a full nREPL server inside our application, including CIDER middleware. Very convenient for development, very convenient for connecting to from Emacs on QA or production. Pretty heavyweight tho'...

seancorfield03:11:19

...we switched that workflow to just being able to start a socket server (based on JVM arguments) on processes in order to debug / update them. Meanwhile, we changed our DEV workflow to start a REPL in our editor, then create and start Components so we can run our apps in the REPL. That's a much better workflow 🙂

mattyulrich03:11:12

Hrm - thanks for the suggestions and color, @seancorfield. I'll give the socket server a shot for this deployment and see how that works out. Have a great night!

hkjels12:11:32

I’m getting goog is not defined when I refresh on a path other than root, so I’m guessing boot does not set asset-path correcly. How do I do that manually with boot?

hkjels13:11:34

putting asset-path in the compiler-options solved it

phreed17:11:44

I am learning to use fulcro and they start off explaining how to use [figwheel in lein](https://github.com/fulcrologic/fulcro/blob/develop/GettingStarted.adoc#running-figwheel). What is the current recommendation about live coding with boot? I see these options: https://github.com/adzerk-oss/boot-reload https://github.com/aJchemist/boot-figwheel https://github.com/boot-clj/boot-figreload

juhoteperi17:11:40

@phreed boot-reload is probably the most stable / polished of those, figwheel based boot-figreload has a few more features (should support Node, reconnects after restart etc.). Boot-reload/figreload compose together with boot-cljs and use filesets and other Boot features. Boot-figwheel just uses file watcher etc. from Figwheel and doesn't work together with other Boot tasks, at least the same way as boot-reload/figreload.

nha17:11:39

I’ve used boot-reload with an om.next app (I don’t think boot-figwheel existed at the time). Some parts of reloading are a bit tricky, but mostly on the om end of things - I don’t remember having to dive into boot-reload.

juhoteperi17:11:47

One thing Boot-reload has in comparison to Figreload, I think, is that it can show compile warnings/exceptions from other tasks besides Cljs compilation. My Less4clj and Sass4clj compilers use this.

phreed18:11:42

Thanks for the advice. @nha et al.