Static content (css, etc.) 404's when served from gunicorn about adl_lrs HOT 1 CLOSED

hey stever, try this: http://stackoverflow.com/questions/12800862/django-static-files-under-gunicorn

Just to be clear, the extra pages and static files have little to do with the experience api. They're there mainly to give some sort of user interface out of the box.

And for the record, if you're just doing dev and local testing of the LRS, you could easily use the django development server, like you said, which will serve the static files. And if you are going to host this publicly you will need to add some http proxy to serve static files and pass off the rest to gunicorn and the LRS.. We use nginx, which was pretty easy to set up. If I get a chance after 1.0 development, I'll try to write up a wiki on how to stand up nginx as an http proxy, though you can probably read the documentation for django, gunicorn and nginx and set it up w/o too much effort.

I don't see this as a bug. I'm changing it to a question and closing it.

from adl_lrs.