Forums

django hosting steps for existing project

Hi, I want Detail Web Hosting Information and Steps for django 1.5 version.

I created new project and activated admin but getting error ImproperlyConfigured at /admin/

You haven't set the database ENGINE setting yet.

please provide me configuration for "database ENGIN"

There is a tutorial on our wiki with instructions for setting up Django 1.5 in a virtualenv and the configuration details for databases (assuming you're using MySQL) are on the "Databases" tab.

hello I followed the instruction but after making changes in WSGI.py file,I should see the "it worked!" Django page.but i can see """" Hello,World! This is the default welcome page for a PythonAnywhere hosted web application. Find out more about how to configure your own web application by visiting the web app setup page"""

please tell i am on right path or not.

Looks like that's fine ("it worked" is the important clue)

It didn't work. He's getting a 404 now...:(

Of course it's also version 1.3.7 of Django, so something didn't go right from the tutorial. Probably need to recheck your steps malharvntech.

i am using django 1.5.2 and i followed instruction on website https://www.pythonanywhere.com/wiki/VirtualEnvForNewerDjango but After following steps.i am getting this on my domain name """" Hello,World! This is the default welcome page for a PythonAnywhere hosted web application. Find out more about how to configure your own web application by visiting the web app setup page"""

So i am asking. is it right or wrong because I should see the "it worked!" in my domain name according to https://www.pythonanywhere.com/wiki/VirtualEnvForNewerDjango

What URI are you going to? When I go to http://malharvntech.pythonanywhere.com/ I get a 404. When I go to http://malharvntech.pythonanywhere.com/admin/ it reports Django version 1.3.7...

I'd read more though the page, but I have a meeting to leave for.

I see a Django 404 page at http://malharvntech.pythonanywhere.com, so it looks like you may have got past the issue above.

For the record, the most likely cause of the difference above is not following the instructions that say you should edit your WSGI file.