This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-21
Channels
- # admin-announcements (4)
- # aleph (1)
- # beginners (15)
- # boot (55)
- # braveandtrue (5)
- # cider (20)
- # clara (10)
- # cljs-dev (13)
- # cljsrn (8)
- # clojure (52)
- # clojure-austin (30)
- # clojure-brasil (2)
- # clojure-india (1)
- # clojure-italy (2)
- # clojure-nl (1)
- # clojure-russia (72)
- # clojure-sdn (9)
- # clojure-taiwan (2)
- # clojure-uk (45)
- # clojurebridge (3)
- # clojured (1)
- # clojurescript (46)
- # core-matrix (1)
- # cryogen (1)
- # cursive (43)
- # datascript (12)
- # datomic (57)
- # devcards (54)
- # emacs (6)
- # funcool (21)
- # hoplon (335)
- # jobs (15)
- # jobs-rus (40)
- # ldnclj (2)
- # lein-figwheel (20)
- # off-topic (59)
- # om (157)
- # onyx (29)
- # parinfer (2)
- # pedestal (26)
- # proton (9)
- # protorepl (2)
- # reagent (3)
- # ring-swagger (4)
- # spacemacs (2)
- # untangled (17)
Hi @bhauman, do you have a few minutes to talk about PR#360 on lein-figwheel? (`:server-opts` for http-kit
)
Sweet. You mentioned in your comment that I'd have to create my own server, which is fine with me, but it's not abundantly clear how I'd go about injecting my own server into the lein figwheel dev
process.
Ahh, So, separate JVM's, one of them running the figwheel server, and another serving the app?
OK, cool. Didn't even think of running separate servers... Thanks, I'll give it a shot!
the main take away here is that the figwheel communication connection is a websocket that by default runs at localhost:3449 and your clojurescript/figwheel client code will automatically connect to it
For sure. This whole workflow is so new to me that it's tough to see the obvious sometimes 😉
I need to write a FAQ as this is the number one place where a lot of folks get tripped up
Sounds good. I just recently started with Clojure/script + Figwheel, so I'll shoot over some of the things that I ran into if I can ever get out from under all of these projects...