If you're just trying to host stuff you're developing (for yourself) you
could host it locally, either just using the dev server or using a
lightweight server like lighttpd.
If you actually want to deploy the sites, I'm still no use... But Bluehost
do offer pro-rated refunds (if you're 2 months in
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
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 aro
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/80557/
/myproject/home/views.py: http://dpaste.com/80558
4 matches
Mail list logo
