Site update once again, and a warning about django and httpd
First for the site update (and know some stuff is still broken):
1 – I added feeds back to the web site, so RSS is now working correctly. You can add the link here:
http://www.thedarktrumpet.com/feeds/blog/
I will add a link later ont he main site.
2 – I updated my contact form. before it didn’t, work, now it does. I created a project for doing it and it works OK now.
Now for the problems:
1. Update your httpd configuration file. I’ve had the issue where when I uploaded my new code, that my contact form didn’t work. The error message said that it couldn’t find my module – yet it was in my path. What I didn’t realize is that after reading the documentation that you need to be sure to add the parent directory of your modules. So for example, if you use a project directory called sitecode like I do, then be sure to add the directory that contains sitecode as well as sitecode to your PythonPath in your httpd.conf file.
2. If you utilize a separate file for your settings.py (say you use a different database), then ensure that they stay similar and you check this file first. I didn’t, and spent 2 hours installing Python 2.5, modules and all that. I’m not too upset over that, although I really need to roll back to 2.4 on CentOS.
I thought quite a bit about how I can better make sure things work. A solution that’s possible is if you have your project uploaded to your server, then make it “production ready” then run your unit tests. I would have caught #2, but unfortunately #1. I’m kinda curious if the project is uploaded to a sub-domain of a site, and tests run then, and if they pass then put it on full production, if it’d work better. I’m thinking it would – but this is something I did some time ago on my mac, and that’s run CentOS5 with the same general settings as this has. Having a place to push and test to would have probably been a good idea.
Ideas on how you solved this problem would be helpful.
