@execthis, thanks for your PR! By analyzing the history of the files in this pull request, we identified @mgoffin and @dicato to be potential reviewers.

Btw. where can i find the wiki files for "Production grade CRITs install" to update them as well? Thanks

Is there a specific reason why you want to move what we consider the "default" directory of /data/crits to something else? Functionally it shouldn't matter that things are in /data/crits as long as configuration is properly set.

For clarification, I'm looking at the symlink you are creating, and the aliases you are generating pointing to that location.

its just a symlink who points to /data/crits/extras/www. everything is still located under /data/crits. Otherwise I had to create a directory section for every alias or dir inside the virtual host because of "Require all denied" on root from apache2.conf:

<Directory />
 	Options FollowSymLinks
 	AllowOverride None
 	Require all denied
 </Directory>

I tried to give access to them like this with no success:

<Directory "/var/www/crits/(static|js|css|ext|images|img|new_images|plugin)">
       Options Indexes FollowSymLinks MultiViews
       AllowOverride All
       Order allow,deny
       allow from all
</Directory>

Im wondering why Directory directives are not recursively valid? So I decided to create a symlink to prevent having a lot of directory directives inside the virtual host configuration. Do you have a better approach?

Thanks

I don't. I'm just trying to play devil's advocate here to determine if the symlink having to be created by the admin of the box is a necessary step as opposed to us having a configuration which already points to the necessary directories where the admin is expected to explode the code base.

I'll try again tomorrow without the symlink. I just read that directory directives are applied recursively... normally: http://httpd.apache.org/docs/current/sections.html#file-and-web