Apache上的Django Admin静态文件

Question

There are quite a few posts on here regarding the same subject, I've tried as many as I thought applicable. Yet, I still have this error. Everything is being served fine for a django site I've built except the static files for admin.

Versions: Django 1.6, Apache 2.4.7, Ubuntu 14.04

Ok - I have ran manage.py collectstatic and here is the static folder:

/srv/bahai-site/bahai-site/soul/static

This contains four folders: 1) admin/ 2) bootstrap/ 3) core/ and 4) flags/

Within these folders, I can see all expected static files and that they contain the code I'd expect.

When looking at a static file on the site itself, something like /static/core/css/desktop_992.css loads correctly while /static/admin/css/base.css throws a 404.

Apache directives in http.conf:

Alias /static/ /srv/bahai-site/bahai-site/soul/static/

<Directory /srv/bahai-site/bahai-site/soul/static/>
Allow from all
</Directory>

WSGIScriptAlias / /srv/bahai-site/soul/soul/wsgi.py
WSGIPythonPath /srv/bahai-site/soul/soul:/srv/envelope/bahai-site/lib/python2.7/site-packages

<Directory /srv/bahai-site/soul/soul>
<Files wsgi.py>
Allow from all
</Files>
</Directory>

Side question: notice the WSGIScriptAlias and WSGIPythonPath only contains one "bahai-site/" directory level, instead of the two that actually exist after "/srv/". Why is the site running fine? Shouldn't that be causing a problem?

Anyway, what am I doing wrong here? How do I get these admin static files up and running?

Answer 1

as far as the pythonpath is concerned I personally don't include that in my apache virtual host config file and it works. Maybe that's not needed? Honestly I'm not all that well versed in server installations. It defintely seems like a permission issue.

I would run collectstatic using sudo, then I would also make sure the static folder has www-data group permission which is the permission apache uses out of the box.

If you need help setting permissions on a folder in Ubuntu check out this link here. https://askubuntu.com/questions/244406/how-do-i-give-www-data-user-to-a-folder-in-my-home-folder

Answer 2

The problem was that I had updated two different configuration files for Apache with competing directives.

Note to Other Beginners:

Directives (ie things like ...) can be placed in any file in the apache2 root -- in my case that was any file within /etc/apache2/. (Question to advanced users: is this only for Ubuntu? Or pretty much any Linux/Unix?) This will confuse you because, if you solve a problem using information from multiple online posts/documents, you'll likely have a smorgasbord of various people's Apache configuration preferences/styles. Hence my problem.

As a beginner, you're probably expecting to see some kind of single location you can put your configurations/customizations (in this case directives) into. That's not the case on Apache. You can put any of these anywhere. This is probably good once you advance your knowledge of Apache but it sucks when you're starting out.

My fix here was to go through all the files I touched in the /etc/apache2/ folder and consolidate any rules into one place. This lead to me removing duplicate/conflicting rules, which solved the problem.

Now I think I need to talk to a therapist....