If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. In February 2021 we are working to remove any of these links and potential cookies from the site.
Siteground awstats archive#
Some older blog posts and archive pages that may add cookies from Amazon Associates or Share A Sale. We also record the visitor’s IP address and browser user agent string to help spam detection. This will send an email to the site owner, Penny Shima Glanz. When you fill out and submit the contact form, you provide us with the data shown in the form. We also record the IP address and browser user agent string to help spam detection. This is used to display your comment on the site. When you leave a comment on this site, you provide us with the data shown in the comments form. This information is used to contact you for purposes directly related to the transaction. When you do certain transactions via our website, you provide certain identifying information during the course of the transaction. Wherever that file may be in your setup, open it and add this line somewhere in the server block.We respect your privacy and are committed to protecting it. For example this site is served by the file /etc/nginx/sites-enabled/. If you follow the standard nginx practice, your config file should be in /etc/nginx/sites-enabled/. Now we need to edit our individual nginx config file to use this log format. '"$http_user_agent" "$http_x_forwarded_for"' '$status $body_bytes_sent "$http_referer" '
Open up /etc/nginx/nf and add these lines: log_format main '$remote_addr - $remote_user "$request" ' If you don’t customize your Nginx log format then you can skip this section, but make a note of where Nginx is putting your logs, you’ll need that in the next step. To get AWStats working the next step is to create our config files and build the stats, but first I like to overcomplicate things with a custom log format for Nginx. You can double-check that the database files exist by looking in the directory /usr/share/GeoIP/ and verifying that there’s a file named GeoIP.dat. That should take care of the GeoIP stuff.
Siteground awstats install#
Once cpan is set up, install GeoIP: install Geo::IP If you’ve already got cpan set up, you can skip to the next step: make install If this is your first time in cpan you’ll need to run two commands to get everything set up. Next you need to fire up the cpan shell: cpan Here’s what worked for me.įirst we need build-essential and libgeoip: sudo apt install libgeoip-dev build-essential
Because I like to have some geodata in my stats, I also installed the tools necessary to use the AWStats geoip plugin. This will install the various tools and scripts AWStats needs. The first step is to install the AWStats package from the Ubuntu repositories: sudo apt install awstats Here’s how I’ve managed to get AWStats installed and running on Ubuntu 18.04, Ubuntu 20.04, Debian 10, and Debian 11. AWStats just analyzes your visitors’ footprints. There’s no spying, no third-party code bloat. It parses your server log files and tells you who came by and what they did. If you’d like some basic data about your site’s visitors, but don’t want to let spyware vendors track them around the web, AWStats makes a good solution. I’ve updated the guide so that the commands work on both Debian 11 and Ubuntu 20.04.
Siteground awstats update#
Update Sept 2021: I still use this method and it still works.
0 kommentar(er)
