Thanks guys, both posts helped. Cheers.
On Tuesday, 1 May 2012 01:51:08 UTC+8, HarpB wrote: > > It is much better to use Apache for static files than Django. You can > still run DJango for data validation, but all static content is typically > served via Apache. In your virtualhost, you should proxy the /static/ > endpoint to the /static/ folder in Django app. > > On Sunday, April 29, 2012 5:39:15 AM UTC-7, collectiveSQL wrote: >> >> Hi Everyone, >> >> I'm working on a heavily animated web site using the html5 canvas tag. >> Its mainly made of html, javascript and css static files and I'd like >> to integrate the Google Identity Toolkit for an Oauth 2.0 account >> chooser for signup and registration. >> >> The first question is Django a good candidate for serving up mainly >> static files and using a small Django app for authentication? >> >> And secondly what performance impact would this have over straight >> apache? >> >> More info: >> >> 1. Static web files such as html, javascript and css are stored on >> Amazon AWS S3 >> 2. Data is loaded via oData using jsdata for animations >> 3. Amazon AWS EC2 is used to scale apache web servers >> >> Thanks in advance. > > -- 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/-/fD37MNVMpbUJ. 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.
