haikuprojects/haikuports
1
0
Fork 0
mirror of https://github.com/yann64/haikuports.git synced 2026-05-05 06:28:55 +02:00
Code Issues Packages Projects Releases Wiki Activity

lighttpd: bump to 1.4.42, with mod_geoip and 6 other modules. (#851)

Browse Source 
* This release of lighttpd comes with 7 new modules: mod_deflate,
  mod_authn_{file,gssapi,ldap,mysql}, mod_uploadprogress and
  mod_geoip.
* The GeoIP module is being added in a separate sub-package to limit
  the dependency on the geoip package to that sub-package only.
* Add a quickstart-geoip.txt and a demo geoip page for novice users.
* In lighttpd.conf don't use paths that change when the package is
  updated.
* Keep lighttpd.pid in /var/run instead of /var.
* Switch SOURCE_URI from tar.gz to tar.xz ;-)
This commit is contained in:
fbrosson
2016-11-02 22:56:16 +00:00
committed by waddlesplash
parent 1010d1e0a6
commit 59c43b62f6
5 changed files with 130 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
www-servers/lighttpd/additional-files/quickstart-geoip.txt Normal file
View File

@@ -0,0 +1,20 @@
A GeoIP module is officialy included in lighttpd since release 1.4.42.
To use it you have to download the GeoIP.dat or GeoLiteCity.dat databases from
http://maxmind.com/
You can do so manually, or with the geoipupdate command from the geoipupdate
package or the geoipupdate.sh script from the geoip package (which provides the
libGeoIP.so shared library needed by mod_geoip.)
You will also need to edit /system/settings/lighttpd/conf.d/geoip.conf to
uncomment the line with the geoip.db-filename parameter.
Finally, you will need to edit /system/settings/lighttpd/modules.conf to
enable mod_geoip by uncommenting the line with the following directive:
include "conf.d/geoip.conf"
A demo geoip page is /system/data/www/htdocs/geoip/index.lighttpd.shtml
and can be accessed by pointing your browser to http://yourserver/geoip/
Reminder: GeoIP data is not available for private network addresses as defined
in rfc1918 (e.g. 192.168.x.y) so you won't see any GeoIP data unless you access
your web server from a public IPv4 address.
Warning: You should only expose your web server if you know what you are doing.