@thegeez I see, so you are bringing up your own jetty and then make figwheel work on that, instead of asking figwheel to bring up it's own jetty and configure your routes in addition to what figwheel needs. Right?

@pwrflx no, figwheel start its own jetty and the pedestal app also starts its own jetty. No routes/handlers from the pedestal app are served by figwheel in my setup

@thegeez Didn't you constantly run into cross-origin issues with that? I mean the javascript running will need to use the API provided by pedestal that's on a different origin (in practice it's both localhost but the port number is different, which was enough to trigger cross-origin issues for me..)

I see no warning/error about that in chrome. Also figwheel only sends messages to reload js sources. Any calls in those js sources are to the same app origin (port 8080 for the app in dev). figwheel uses port 3449

@thegeez ah ok I start to get it now. You're using pedestal's Jetty to both server the API and all javascript resources. Figwheel's jetty is just used to have the connection to the repl and notify the browser to reload the javascript (and that reloading I guess also takes place on 8080)

yes

@thegeez this sounds cool. Will give it a try! thanks!