telize

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

commit 766a2991acbef2f70e8e34fa00f291dc5dcb1472
parent 46fd248b92e874bb17e9e111b0039c9e724dc811
Author: Frederic Cambus <fred@statdns.com>
Date:   Sat,  3 Mar 2018 17:34:50 +0100

Account for configuration file rename in README

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

diff --git a/README.md b/README.md @@ -94,9 +94,9 @@ specifying the path to the GeoIP2 database files, within the http block. $geoip2_organization autonomous_system_organization; } -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. +Then deploy the API configuration file `telize.conf` 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, default values of `map_hash_max_size` and `map_hash_bucket_size` variables might be too low and Nginx will refuse @@ -136,7 +136,7 @@ By the following directive: ## CORS Support (Cross-origin resource sharing) Telize has CORS enabled by default since version 1.02. The following variables -defines CORS behavior, within the `telize` configuration file. +defines CORS behavior, within the `telize.conf` configuration file. set $cors "true"; set $cors_origin "*";