When using Figwheel + Devcards at the same time as your own application HTTP server, does it matter if you serve static assets from your app's HTTP server or from Figwheel's embedded HTTP server?

I'm attempting to port the om-next-starter project (https://github.com/jdubie/om-next-starter) to use stuartsierra's component library following the example in https://github.com/bhauman/lein-figwheel#user-content-scripting-with-component . Here's a gist: https://gist.github.com/grzm/f0caa09e5b15500a4b89

Figwheel starts up on 3449, serving up the om app. The jetty-server starts up on 3000. And the om app get's 404's when fetching data from the server.

I'm likely missing something quite basic. Any pointers would be appreciated.

@grzm Which port are you visiting in your web browser?

3449

Try visiting 3000 instead.

If your application is trying to fetch data from the server, it needs to get it from your application server, not Figwheel.

Which, interestingly, answers the question I just asked earlier.

I thought they might be related

3000 gives me a 404 as well. It doesn't serve the app at all.

Is your app server configured to serve static files out of resources/public?

Running the server using just :figwheel-options {:ring-handler server/app} works as expected. index.html, which loads the app, is in resources/public, which I understand is the default for ring. There's no explicit config for resources/public in :app-server. Should there be?

Yes.

you don't happen to know how to configure that, do you? My google fu is failing me.

Depends on your web framework / routing library / etc.

https://github.com/mmcgrana/ring/wiki/Static-Resources is typical.

okay, in that case I believe I do have that configured. It's using ring, and the handler includes (wrap-resource req "public") middleware

oh, crikey. I was visiting , not .

thanks for walking me through it.

You're welcome.