I am configuring a linux webserver to support several different websites, using Django and Apache2. I have Django code for each site, some libraries supporting each of those sites, and the Apache configuration files. Does this layout pose any problems?
home/ |--django_libraries | |--lib_one/ | |--lib_two/ |--sites | |--site_one/ | |--site_two/ | |--site_three/ |--apache_conf/ | |--apache2.conf, etc | |--sites-available/ | |--sites-enabled/ | |--et cetera | |--[mods-enabled and the like left under /etc] |--apache-support/ |--directories with certificates for ssl, authentication files, etc
- This organizes the sites-specific files under one directory. I know where to find things and can back it up, or replicate it, with a single tar statement.
- This seems to allow separate things enough to control access and security with user permissions.
- I don't like to disturb the default Apache configurations under etc/ because I'm a newbie and often consult them. Also I find it less confusing to have the Apache configurations near the Django code.