On Friday, 15 March 2013 10:05:48 UTC, br...@kanka.de wrote: > Because the 'brand' comprises a package manager? > Of course you can ignore it, but once you have, you can not easily go back > to the package-administration. > With the package manager, after having installed apache2, you would > continue: > *aptitude install libapache2-mod-wsgi* > I found that after browsing several blogs - it should be in the Django docs. >
That's a detail restricted to Debian-based brands of Linux. I can't imagine why that should be in the Django docs. The docs themselves link to the mod_wsgi installation documentation, which mentions package managers. > > Same with the *WSGIScriptAlias *that needs to be inserted in apaches > config. > That has nothing to do with Debian, and *is* in the Django docs. https://docs.djangoproject.com/en/1.5/howto/deployment/wsgi/modwsgi/ > Then, what is the connection to the *wsgi.*py that is generated by * > startproject*? > Er, that is what goes *in* WSGIScriptAlias. Again, that is in the docs. In other words, you haven't read the documentation you're complaining about being incomplete. -- DR. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
