caretcaret Posted November 3, 2008 Posted November 3, 2008 Hi, I am using Python with Django. I am new to it and I am learning it. I followed the instructions on the page for Python/Django. I started a small project (for now). The thing is, I used the server that came with Django on my computer, and my project works. When I move it on to HelioHost, it doesn't work. I put the project folder under /public_html/ and have the .htaccess and the dispatch.wsgi in the project folder with the right permissions. Going to my website, http://<website>/<projectfolder> brings up the code of dispatch.wsgi. http://<website>/ gives a directory of /public_html/ because I haven't set up an index page yet (I set Django to provide a page when http://<website>/ is requested). The Django files are .py, should they be .pyc? Am I forgetting to do something (like starting up Django, if there is such a thing), am I doing something wrong, or what?
Ashoat Posted November 3, 2008 Posted November 3, 2008 Try again and see if it works now. If it doesn't: what is your HelioHost username and domain?
caretcaret Posted November 3, 2008 Author Posted November 3, 2008 [withdrawn] and [withdrawn] respectively. Edit: Fixed, withdrawn for privacy.
Ashoat Posted November 3, 2008 Posted November 3, 2008 Okay, I've got it working. You have a few errors you'll have to fix (for instance, you need to switch some paths in settings.py), but you can continue to debug by yourself from here. The issue was that Python needed a temporary directory to store eggs (modules, ie. MySQL and PgSQL).
caretcaret Posted November 3, 2008 Author Posted November 3, 2008 Thanks for the quick fix and the great webhosting!
Ashoat Posted November 3, 2008 Posted November 3, 2008 I have updated the heliohost.org guide with the proper directions. If you experience this problem again, just follow the directions there.
caretcaret Posted November 3, 2008 Author Posted November 3, 2008 OK, I am getting a 500 Internal Server Error now. :\ The error log reports Exception occurred processing dispatch.wsgi, line 9. The cache is still there, I only edited files. I followed the instructions again.
Ashoat Posted November 3, 2008 Posted November 3, 2008 Sorry, that problem is now fixed. I recently upgraded to Django 1.0, and there was a conflict between an old and new version of a file that was causing the error.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now