Thing is I already got my bluehost account for other projects, so getting another host kills my budget. Also the contract is running for another good 10 months so switching now isn't an option either. I only recently started django coding, so now I have to use what I have... But I see what you mean.
Oli Warner wrote: > I apologise in advance for a reply that isn't going to seem > immediately useful. > > Don't host django sites on shared systems that don't wont help users > host their sites with them. Seriously. I've tried both Dreamhost (did > it!) and Bluehost (failed miserably). You spend hours, if not days, > hacking around and you end up with something that is far from ideal. > > With a host that does care about Django, you copy your site onto their > server and it runs. > > If you can afford it ($10/month) I'd seriously suggest a low-end VPS. > They make life even easier. > > On Fri, Aug 14, 2009 at 5:02 PM, Jonas Obrist <ojiido...@gmail.com > <mailto:ojiido...@gmail.com>> wrote: > > > I try to get django (1.0.2) to run on a shared hosting (with python > 2.5.2) through fcgi (with flup 1.0.2). > > I've written a very simple app to test this: > > /myproject/settings.py: http://dpaste.com/80556/ > /myproject/urls.py > <http://dpaste.com/80556/%0A/myproject/urls.py>: > http://dpaste.com/80557/ > /myproject/home/views.py > <http://dpaste.com/80557/%0A/myproject/home/views.py>: > http://dpaste.com/80558/ > > I use this script to run it: > > django.fcgi: http://dpaste.com/80559/ > > with the .htaccess: > > http://dpaste.com/80560/ > > Problem: I get an error when calling the page (using > http://www.ojii.ch/projectsj/django.fcgi): > > Traceback (most recent call last): > File "django.fcgi", line 9, in <module> > WSGIServer(WSGIHandler()).run() > File > > "/home1/ojiich/lib/python2.5/site-packages/flup-1.0.2-py2.5.egg/flup/server/fcgi.py", > line 114, in run > File > > "/home1/ojiich/lib/python2.5/site-packages/flup-1.0.2-py2.5.egg/flup/server/threadedserver.py", > line 84, in run > socket.error: (22, 'Invalid argument') > > Which of course raises a 500 error. > > Anyone got any ideas how to fix this? Been trying everything I could > think of and followed two different guides: > http://www.bluehostforum.com/showthread.php?t=715 > > http://alextreppass.co.uk/blog/2008/11/14/getting-django-working-on-bluehost/ > > No success.... > > Jonas > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. 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 -~----------~----~----~----~------~----~------~--~---
