The main reason I did it this way is to not have a dependency on apache.

We actually deploy awstats most often with Nginx, and in this case it would not make sense to stick the password file in the apache config. Alternatively I could stick it in /etc somewhere, but that would not be standard either.

I am open to ideas ...

Brent

----- Original Message -----
From: "Joseph Hall" <notifications@github.com>
To: "saltstack/salt-contrib" <salt-contrib@noreply.github.com>
Cc: "Brent Lambert" <brent@enpraxis.net>
Sent: Thursday, May 9, 2013 8:22:16 PM
Subject: Re: [salt-contrib] Awstats module added to salt-contrib (#38)



In modules/awstats.py: > @@ -0,0 +1,221 @@
> +'''
> +AWStats Configuration and Update for Static Deployment
> +
> +:maintainer: Brent Lambert <brent@enpraxis.net>
> +:maturity: new
> +:platform: RedHat, Debian Families
> +
> +A module to configure and update awstats deployed in non-dynamic mode, It
> +
> +- Controls access to statistics through basic authentication vi .htpasswd file 

Makes sense. But I still would never advocate a .htpasswd file. There's nothing in there that can't be configured in a the main Apache configs, and enabling them opens up potential security holes to anyone with access to any Apache htdocs, and degrades Apache performance. 

— 
Reply to this email directly or view it on GitHub .