Migrate httpd.conf to .htaccess?

It isn't actually too clear what problem you are trying to solve. Why are you even using that configuration in the first place? It looks like you just copied it from mod_wsgi documentation without understanding what each bit does and started using it when it isn't even appropriate for your setup.

Specifically that example in mod_wsgi documentation was a generic example and not necessarily suited for Django So, rather that trying to fix that configuration to meet some unknown goal, just describe what you need and will tell you what the proper configuration is that you should be using UPDATE 1 Per my comment below, perhaps then use: AliasMatch /tech_eval/(^/*\. Css) /var/www/tech_eval/static/styles/$1 Alias /tech_eval/media/ /var/www/tech_eval/static/media/ Order deny,allow Allow from all WSGIScriptAlias /tech_eval /var/www/tech_eval/scripts/django. Wsgi Order allow,deny Allow from all Txt and favicon.

Ico, or at least don't get them from sub URL site and just stick them direct in the DocumentRoot directory and use those which truly are for whole of site I think it is 'ADMIN_MEDIA_PREFIX' in Django settings module that you then need to change to '/tech_eval/media For Django don't think you even need to CSS alias and that is where this was originally a generic example to show concepts rather than be something which was correct for Django Anyway, everything is then under '/tech_eval' and shouldn't interfere with other applications on same site.

It isn't actually too clear what problem you are trying to solve. Why are you even using that configuration in the first place? It looks like you just copied it from mod_wsgi documentation without understanding what each bit does and started using it when it isn't even appropriate for your setup.

Specifically that example in mod_wsgi documentation was a generic example and not necessarily suited for Django. So, rather that trying to fix that configuration to meet some unknown goal, just describe what you need and will tell you what the proper configuration is that you should be using. UPDATE 1 Per my comment below, perhaps then use: AliasMatch /tech_eval/(^/*\.

Css) /var/www/tech_eval/static/styles/$1 Alias /tech_eval/media/ /var/www/tech_eval/static/media/ Order deny,allow Allow from all WSGIScriptAlias /tech_eval /var/www/tech_eval/scripts/django. Wsgi Order allow,deny Allow from all Just ditch robots. Txt and favicon.

Ico, or at least don't get them from sub URL site and just stick them direct in the DocumentRoot directory and use those which truly are for whole of site. I think it is 'ADMIN_MEDIA_PREFIX' in Django settings module that you then need to change to '/tech_eval/media/'. For Django don't think you even need to CSS alias and that is where this was originally a generic example to show concepts rather than be something which was correct for Django.

Anyway, everything is then under '/tech_eval' and shouldn't interfere with other applications on same site.

I didn't copy it from the mod_wsgi documentation, I copied it from the Django tut, and I know exactly what it does. I have a project called tech_eval; that configuration is specific to that project. I want to somehow encapsulate that configuration so that it doesn't affect my other projects (since httpd.

Conf is "global" in a sense). I think it would be most appropriately placed inside the actual project folder, but I'm open to other solutions. – Mark Oct 8 '09 at 23:12 The tutorial copied it from 'code.google.Com/p/modwsgi/wiki/…; then.

My concern is that configuration is pushing stuff to root of site for something that is at a sub URL. Yes that is what the original example was doing, but do you really want that? Do what want favicon.

Ico and robots. Txt to come from that specific sub URL site? Do you want CSS files to be pushed to root?

Because Alias/AliasMatch take precedence over WSGIScriptAlias, you can prefix LHS with '/tech_eval'. Just change Django settings for media URL root. – Graham Dumpleton Oct 9 '09 at 4:45.

Use VirtualHosts to limit the scope of these lines, and an include per virtual host to organize your config files and keep it from growing unwieldy.

I'm looking at this directive now... do I need multiple IP addresses...? I'm a complete n00b when it comes to this. I've installed phppgadmin recently, and it looks like the Alias for it is set in /etc/apache2/conf.d. Couldn't I just have a file like that for each of my sites?

Are those loaded automatically? – Mark Oct 8 '09 at 7:11 Unfortunately, the way Apache config files are organized varies wildly by distribution.It's enough to make you go nuts sometimes. Look for Include lines in your httpd.

Conf file, probably near the bottom. If the path is a directory, it will include all the files in that directory. – Matt Miller Oct 8 '09 at 13:52 You don't need separate IP addresses for name-based virtual hosts (httpd.apache.

Org/docs/1.3/vhosts/name-based. Html) You DO need separate domain names (or at least, subdomain names) -- which I'm assuming you have because of phrases like "all my sites. " – Matt Miller Oct 8 '09 at 13:55 @Matt: Err..no, I don't have separate domain names for them.

They're just in separate folders. Too cheap to buy domains for a school project :p – Mark Oct 8 '09 at 23:14.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.