Fork me on GitHub
#lein-figwheel
<
2016-06-15
>
bhauman13:06:55

You may need to upgrade your ClojureScript version.

verma20:06:59

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

verma20:06:35

^ edited version number and port

verma20:06:23

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

verma20:06:42

;; 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"}

verma20:06:22

^ this is what I have in [:cljsbuilds :builds 0 :figwheel]

verma20:06:18

creating a test project to test it out

verma20:06:16

ok, confirmed on a new project

verma21:06:08

will continue looking at it

bhauman21:06:40

:websocket-host only manipulates the host name not the port

bhauman21:06:38

This did change

bhauman21:06:45

It was a bug

verma21:06:48

oh ok, I was wondering

verma21:06:22

alright, so the figwheel socket will always connect over 3449?

verma21:06:11

my use case is that my figwheel runs behind a proxy since I have to proxy multiple APIs my cljs app calls into

verma21:06:53

so my web listens on port 80 and everything is proxied under that ... /api/1 /api/2

bhauman21:06:45

Even the figwheel websocket?

verma21:06:55

for now I have opened up port 3449 on my proxy (nginx) and routed traffic through to figwheel-host:3449/figwheel-ws

verma21:06:20

since websocket-host was overriding the port as well, so it felt natural

bhauman21:06:51

You can use :websocket-url

bhauman21:06:19

Look at the new docs on it in the readme.

verma21:06:21

yeah, I noticed a change around that, so that's the recommended approach? (I will update the issue)

verma21:06:14

:thumbsup: for websocket-url though, since I can now do wss for one of my projects 🙂

verma21:06:38

ok, issue updated and closed, thanks @bhauman

verma21:06:42

works as expected :thumbsup:

harold23:06:37

@bhauman: upgrading to the latest clojurescript fixed the warnings right up, thanks!