I read up on Managing Static files in django. Do I need to deploy my static content on a separate server, or will it work fine since I have very little static content? currently, I'm accessing all my css files and images with the actual path name instead of using "{{STATIC_URL}}".

1 Answer
1

You will at least need an HTTP server running on whatever you're running your django project from, and it's highly recommended that you use a separate server for your static files apart from your app logic.

Secondly, it's very bad practice not to use {{ STATIC_URL }} or a similar item. Absolute paths are evil. If the project changes machines, or if it needs multiple versions, etc. These paths could very well change.

I can't see why the OP would need a separate server for such a small site. Assuming they're using mod_wsgi for the dynamic part, the same Apache instance is fine for the static part.
–
Daniel RosemanAug 30 '12 at 8:36

You wouldnt need a separate box but you'd need a web server or config running on the box capable of serving static files, separate from the django setup. AFAIK anyhow, and that's what djangos docs recommend.
–
Alex HartAug 30 '12 at 11:58

But as I said, if they're using mod_wsgi, they already have that server: Apache. The docs give a perfectly good example of how to serve static and dynamic content from the same instance.
–
Daniel RosemanAug 30 '12 at 12:01