The doc at http://docs.djangoproject.com/en/dev/howto/static-files/ should fix that css 404 problem. As far as web faction I know a fair number of people in the Django community are happy there. I personally use Linode (http://www.linode.com/index.cfm), they've been the best VPS I've ever dealt with. As long as you are comfortable administering your own server they're my recommendation. Which ever host you decide to go with, try to get as much RAM as you can. Django can run on relatively little RAM but the more you can get, the better it will run/scale.
____________________________ Sean O'Connor http://seanoc.com On Mon, Oct 13, 2008 at 10:51 PM, Orion Vianna < [EMAIL PROTECTED]> wrote: > Sean O'Connor wrote: > > It looks like the auth and session middleware are not active. Those > errors > > generally happen when those middleware are expected to be available but > are > > not. Looking at the stack trace provided, the only middleware which > Django > > thinks are active are > > "('django.middleware.locale.LocaleMiddleware', > > 'satchmo.shop.SSLMiddleware.SSLRedirect', > > 'satchmo.recentlist.middleware.RecentProductMiddleware')". > > Once you can figure out why your middleware are not loading properly you > > should be able to fix your problem. > > Some suggestions include: > > > > - Make sure that if you are explicitly setting the > > DJANGO_SETTINGS_MODULE environment variable that is is set properly. > > - Check that you have > > 'django.contrib.sessions.middleware.SessionMiddleware' > > and 'django.contrib.auth.middleware.AuthenticationMiddleware' in your > > middleware list. > > - Check that 'MIDDLEWARE_CLASSES' has been only defined once. Also > make > > > It was defined twice and its fixed now. Thank you very much! It worked. > I'm now getting 404 for the css files, I will look more in to it. > > > > > > In regard to the web server bit, you definitely want to develop against > the > > django web server, apache is a good bit more complex to setup and gets a > bit > > odd if you don't reload it every time a python file is changed. That > being > > said NEVER run the Django server in a production environment. Apache or > > some other standard web server would be best in a production deployment. > > > > Hope this helps and feel free to send any more questions my way. > > > I'm aware that the webserver included in Django is not for production. > Thanks for the heads up and all the great information. > Which web host would you recommend? I'm looking in to WebFaction do you > know anything about them? > _______________________________________________ > Mid-Hudson Valley Linux Users Group http://mhvlug.org > http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug > Upcoming Meetings (6pm - 8pm) MHVLS Auditorium > Sep 3 - Porkchop - The Areas of My Expertise > Oct 1 - Ubikeys > Oct 4 - Linux Fest > Nov 5 - Releasing Open Source Software > Dec 3 - TBD > > _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Sep 3 - Porkchop - The Areas of My Expertise Oct 1 - Ubikeys Oct 4 - Linux Fest Nov 5 - Releasing Open Source Software Dec 3 - TBD
