When I deploy it, I modified the apache2
staging.validation.linaro.org.conf, only to add:
Alias /squidreport "/var/www/squidanalyzer"
<Directory /var/www/squidanalyzer>
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order deny,allow
allow from all
</Directory>
Just like the /linaro/images section, I feel strange that
http://staging.validation.linaro.org/images can work, while
http://staging.validation.linaro.org/squidreport only get some django
warning message, Could someone point out what's wrong? You can see the
error log by http://staging.validation.linaro.org/squidreport
The squidanalyzer html output is already in /var/www/squidanalyzer/.
On 29 May 2012 17:55, Spring Zhang <[email protected]> wrote:
> Hi,
>
> I think we can deploy a Squid analyzer on the v.l.o, which will visualize
> the squid access log. Though it doesn't hit the big size tarball caching
> issue, but it's useful for the squid monitoring. I've deployed one on my
> own PC, seems cool.
>
> http://squidanalyzer.darold.net/<http://squidanalyzer.darold.net/install.html>
>
> --
> Best wishes,
> Spring Zhang
>
>
--
Best wishes,
Spring Zhang
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
