On Sunday, December 30, 2012 6:01:24 PM UTC+1, Amirouche wrote: > > Héllo Stefano, > > On Sunday, December 30, 2012 1:27:12 PM UTC+1, Stefano Tranquillini wrote: >> >> Hi all. >> in the appfog ML we were fighting again the possibility to serve static >> file in django without using an external server. >> So far AF does not provide a setup of the server to split the server in >> static and dynamic (django) folders. >> so, one of the solution is to use this >> >> # urls.py >> urlpatterns += patterns('', >> url(r'^static/(?P<path>.*)$', 'django.views.static.serve', { >> 'document_root': settings.STATIC_ROOT}) >> ) >> >> but, is it ok to use this trick in django or will it lead to problems >> (aka memory problems and stuff like that)? >> > > The documentation state «Again, this view is *not* hardened for > production use» [1] > > What is the particular issue your are facing ? Maybe tproxy [2] can help. >
the problem is that the appfog server does not provide a way to set up static part. so for convenience i (we) tried to use a workaround for solving the problem. ciao > > Regards, > > Amirouche > > [1] > https://docs.djangoproject.com/en/dev/howto/static-files/#django.views.static.serve > [2] https://github.com/benoitc/tproxy > >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/_Rh0njYy--UJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.