This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-05
Channels
- # beginners (23)
- # boot (84)
- # braid-chat (2)
- # bristol-clojurians (1)
- # cider (53)
- # cljs-dev (34)
- # cljsrn (13)
- # clojure (138)
- # clojure-dusseldorf (5)
- # clojure-italy (1)
- # clojure-russia (164)
- # clojure-uk (41)
- # clojurescript (80)
- # clr (2)
- # core-async (6)
- # core-logic (25)
- # core-matrix (14)
- # cursive (10)
- # data-science (4)
- # datomic (4)
- # emacs (3)
- # funcool (6)
- # hoplon (127)
- # jobs-discuss (4)
- # keechma (36)
- # ldnclj (5)
- # lein-figwheel (5)
- # off-topic (5)
- # om (155)
- # onyx (72)
- # overtone (16)
- # parinfer (39)
- # planck (3)
- # protorepl (1)
- # re-frame (11)
- # reagent (5)
- # untangled (22)
Hi all,
I’m struggling with a concept and was hoping for a little bit of help in terms of configuration. I have a cljs-client
and a cljs-server
(node, express). The client is fairly straight forward when running with figwheel
as it just gets served up at localhost:3449
. I built the server following this pattern: https://gist.github.com/bhauman/c63123a5c655d77c3e7f and it also correctly is watched by figwheel
and hot reloads my changes to the api port (3000). The problem I’m having is that because my server runs on a different port than my client I cannot make requests to that server from the client without CORS errors. So the question is, is there anyway to bind/proxy the cljs-server
under the 3449
port as well? Am I thinking about this wrong?
Thanks!
@comamitc: what about adding CORS headers to your server? that sounds like a quick solution to me
Here is my project.clj
in case it helps: https://gist.github.com/comamitc/96abdf61d66ea7473b020c629b7011a5