telize

High performance JSON IP and GeoIP REST API (IP Geolocation)
Log | Files | Refs | README | LICENSE

commit 83c12abc13bf8293f6bbd40e55aff2b728576226
parent 1d7b7ecab48d0547aa1f290f3b27496884046855
Author: Frederic Cambus <fcambus@users.sourceforge.net>
Date:   Wed, 16 Jul 2014 00:36:00 +0200

Documentation update

Diffstat:
MREADME.md | 8++++++++
1 file changed, 8 insertions(+), 0 deletions(-)

diff --git a/README.md b/README.md @@ -79,6 +79,7 @@ Edit `nginx.conf` to include `timezone.conf`, `timezone-offset.conf` and to add ... include /etc/nginx/timezone.conf; + include /etc/nginx/timezone-offset.conf; geoip_country /usr/share/GeoIP/GeoIP.dat; geoip_city /usr/share/GeoIP/GeoLiteCity.dat; @@ -92,6 +93,7 @@ Edit `nginx.conf` to include `timezone.conf`, `timezone-offset.conf` and to add ... include /etc/nginx/timezone.conf; + include /etc/nginx/timezone-offset.conf; geoip_country /usr/share/GeoIP/GeoIPv6.dat; geoip_city /usr/share/GeoIP/GeoLiteCityv6.dat; @@ -101,6 +103,12 @@ Edit `nginx.conf` to include `timezone.conf`, `timezone-offset.conf` and to add Then deploy the API configuration file `telize` to the appropriate location on your system, and reload Nginx configuration. If you are behind a load balancer, read the next section. +Depending on existing configuration, the `map_hash_max_size` and `map_hash_bucket_size` sizes might be set too low and Nginx will refuse to start. If this happens, please add the following directives in the `http` block. + + map_hash_max_size 8192; + map_hash_bucket_size 64; + + ## Telize and Load Balancers