This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-15
Channels
- # admin-announcements (7)
- # alda (1)
- # aws-lambda (1)
- # beginners (12)
- # boot (20)
- # cider (59)
- # cljs-dev (4)
- # cljsrn (69)
- # clojure (232)
- # clojure-austin (3)
- # clojure-austria (1)
- # clojure-belgium (2)
- # clojure-canada (3)
- # clojure-dev (16)
- # clojure-greece (33)
- # clojure-nl (4)
- # clojure-quebec (12)
- # clojure-russia (12)
- # clojure-spec (27)
- # clojure-uk (38)
- # clojurescript (29)
- # community-development (7)
- # component (53)
- # core-async (16)
- # core-logic (1)
- # datascript (7)
- # datomic (11)
- # editors (7)
- # emacs (69)
- # hoplon (157)
- # keechma (1)
- # lambdaisland (2)
- # lein-figwheel (31)
- # leiningen (8)
- # mount (3)
- # off-topic (11)
- # om (23)
- # onyx (64)
- # planck (2)
- # re-frame (18)
- # reagent (21)
- # specter (118)
- # untangled (145)
- # yada (1)
I just upgraded to 0.5.4-3 and it seems like :websocket-host
has no effect 😕 .. the client always tries to connect to localhost:3449
anyone else seeing this or am I screwing this up? .. my lein figwheel
is running inside a docker instance and I get the index.html
served correctly through localhost
;; If no code is to be run, set :figwheel true for continued automagical reloading
:figwheel {:on-jsload "teamchat.core/on-js-reload"
:websocket-host "localhost"}
logged an issue here: https://github.com/bhauman/lein-figwheel/issues/431
my use case is that my figwheel runs behind a proxy since I have to proxy multiple APIs my cljs app calls into
for now I have opened up port 3449 on my proxy (nginx) and routed traffic through to figwheel-host:3449/figwheel-ws
yeah, I noticed a change around that, so that's the recommended approach? (I will update the issue)