Home/ Questions/Q 8939745
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T10:53:12+00:00

I have found a few questhons re my problem, you the solutions didn’t help

  • 0

I have found a few questhons re my problem, you the solutions didn’t help me so I started a new question. Basically that’s how I see the admin page
no css/no js/ no images

Apache’s config: 

<VirtualHost *.*.*.*:80>
    ServerName ********.org
    ServerAdmin ****@******.org

    WSGIScriptAlias / /var/www/webproxy/webproxy/wsgi.py

    DocumentRoot /var/www/cgi-bin/
    ScriptAlias /cgi-bin/ /var/www/cgi-bin/

    ErrorLog /var/www/webproxy/apache/error.log

LogLevel warn

CustomLog /var/www/webproxy/apache/access.log combined

Alias /media/ "/var/www/webproxy/media/"

<Directory "/var/www/webproxy/media/">
    Options Indexes MultiViews FollowSymLinks
    AllowOverride None
    Order deny,allow
    Allow from all
</Directory>

<Directory "/var/www/webproxy/static/">
    Order deny,allow
    Allow from all
</Directory>

This is what I have in urls.py:

from django.conf.urls.defaults import *
from django.contrib import admin
admin.autodiscover()

from core import urls as core_urls

from settings import MEDIA_ROOT, WEBPROXY_MEDIA_ROOT

urlpatterns = patterns('',
    (r'^admin/', include(admin.site.urls)),
    (r'^media/(?P<path>.*)$', 'django.views.static.serve', {'document_root': MEDIA_ROOT}),
    (r'^ui/(?P<path>.*)$', 'django.views.static.serve', {'document_root': WEBPROXY_MEDIA_ROOT}),
)

settings.py:

MEDIA_ROOT = '/var/www/webproxy/media/'
STATIC_ROOT = '/var/www/webproxy/static/'
WEBPROXY_MEDIA_ROOT = '/var/www/webproxy/static/media/'

I’m not sure what’s wrong here. Any help would be really appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    First, you shouldn’t be serving the static files via django.views.static.serve in production as that is meant to be used only for local development (read docs here):

    There may be files other than your project’s static assets that, for
    convenience, you’d like to have Django serve for you in local
    development.

    Second, your Django Admin static files reside under the location Django was installed at. I find using directly these files a better solution than copying (or symlink’ing) the Django admin static files under my own static files directories.

    Example Django static files location on my server: 

    /usr/local/lib/python2.7/dist-packages/django/contrib/admin/static/admin/;

    Therefore in your web server config you have to point the url /media/admin to 

    [my_django_location]/contrib/admin/static/admin/

    If you’re doing things locally, then you might need another entry in your urls.py:

    (r'^admin/static/(?P<path>.*)$', 'django.views.static.serve', '/path/to/your/admin/files/'),
    • 0