[Git][debian-gis-team/libapache2-mod-tile][master] Don't install site configuration.
Bas Couwenberg
gitlab at salsa.debian.org
Fri Jul 19 12:26:51 BST 2019
Bas Couwenberg pushed to branch master at Debian GIS Project / libapache2-mod-tile
Commits:
0b44561a by Bas Couwenberg at 2019-07-19T11:20:04Z
Don't install site configuration.
- - - - -
3 changed files:
- debian/changelog
- debian/libapache2-mod-tile.install
- − debian/tileserver_site.conf
Changes:
=====================================
debian/changelog
=====================================
@@ -20,6 +20,7 @@ libapache2-mod-tile (0.4+git20170108-e25bfdb-1) UNRELEASED; urgency=medium
* Add patch to fix manpage section for renderd.
* Update libapache2-mod-tile packaging for 2.4.
* Add override for web-application-depends-on-apache2-data-package.
+ * Don't install site configuration.
-- Bas Couwenberg <sebastic at debian.org> Sun, 14 Jul 2019 13:26:28 +0200
=====================================
debian/libapache2-mod-tile.install
=====================================
@@ -1,5 +1,4 @@
debian/tile.load etc/apache2/mods-available
-debian/tileserver_site.conf etc/apache2/sites-available
slippymap.html usr/share/libapache2-mod-tile
munin/mod_tile* usr/share/munin/plugins
openstreetmap-tiles-update-expire usr/bin
=====================================
debian/tileserver_site.conf deleted
=====================================
@@ -1,164 +0,0 @@
-# This is the Apache server configuration file for providing OSM tile support
-# through mod_tile
-
-<VirtualHost *:80>
- ServerAdmin webmaster at localhost
-
- ServerName tile.mytileserver.org
- ServerAlias a.tile.mytileserver.org b.tile.mytileserver.org c.tile.mytileserver.org
- DocumentRoot /var/www
-
- ###
- ###
- # increase the log level for more detailed information
- LogLevel info
-
-# You can manually configure each tile set with AddTileConfig or AddTileMimeConfig.
-# The first argument is the URL path relative to this virtual host
-# under which a tile set is served. The second argument specifies the
-# name of the tile set. This is used in the communication with renderd
-# and is the directory under which (meta)tiles are stored on disk.
-#
-# By default (AddTileConfig) mod_tile assumes you are serving png files, however,
-# mod_tile can also serve arbitrary other tile types such as javascript vector tiles,
-# assuming the backend render daemon can handle the file type.
-# To this purpose AddTileMimeConfig takes a 3rd agument, the file extension and it
-# will guess the correct mimetype from it. If the mime type is not set correctly automatically,
-# you need to use the configuration file route, where you can specify the mimetype and file extension
-# independently.
-#
-# AddTileConfig /folder/ TileSetName
-# AddTileMimeConfig /folder2/ TileSetName2 js
-
-# Alternatively (or in addition) you can load all the tile sets defined in the configuration file into this virtual host
- LoadTileConfigFile /etc/renderd.conf
-
-# Timeout before giving up for a tile to be rendered
- ModTileRequestTimeout 3
-
-# Timeout before giving up for a tile to be rendered that is otherwise missing
- ModTileMissingRequestTimeout 10
-
-# If tile is out of date, don't re-render it if past this load threshold (users gets old tile)
- ModTileMaxLoadOld 2
-
-# If tile is missing, don't render it if past this load threshold (user gets 404 error)
- ModTileMaxLoadMissing 5
-
-# Socket where we connect to the rendering daemon
- ModTileRenderdSocketName /var/run/renderd/renderd.sock
-
-##
-## Options controlling the cache proxy expiry headers. All values are in seconds.
-##
-## Caching is both important to reduce the load and bandwidth of the server, as
-## well as reduce the load time for the user. The site loads fastest if tiles can be
-## taken from the users browser cache and no round trip through the internet is needed.
-## With minutely or hourly updates, however there is a trade-off between cacheability
-## and freshness. As one can't predict the future, these are only heuristics, that
-## need tuning.
-## If there is a known update schedule such as only using weekly planet dumps to update the db,
-## this can also be taken into account through the constant PLANET_INTERVAL in render_config.h
-## but requires a recompile of mod_tile
-
-## The values in this sample configuration are not the same as the defaults
-## that apply if the config settings are left out. The defaults are more conservative
-## and disable most of the heuristics.
-
-
-##
-## Caching is always a trade-off between being up to date and reducing server load or
-## client side latency and bandwidth requirements. Under some conditions, like poor
-## network conditions it might be more important to have good caching rather than the latest tiles.
-## Therefor the following config options allow to set a special hostheader for which the caching
-## behaviour is different to the normal heuristics
-##
-## The CacheExtended parameters overwrite all other caching parameters (including CacheDurationMax)
-## for tiles being requested via the hostname CacheExtendedHostname
-#ModTileCacheExtendedHostname cache.tile.openstreetmap.org
-#ModTileCacheExtendedDuration 2592000
-
-# Upper bound on the length a tile will be set cacheable, which takes
-# precedence over other settings of cacheing
-ModTileCacheDurationMax 604800
-
-# Sets the time tiles can be cached for that are known to by outdated and have been
-# sent to renderd to be rerendered. This should be set to a value corresponding
-# roughly to how long it will take renderd to get through its queue. There is an additional
-# fuzz factor on top of this to not have all tiles expire at the same time
-ModTileCacheDurationDirty 900
-
-# Specify the minimum time mod_tile will set the cache expiry to for fresh tiles. There
-# is an additional fuzz factor of between 0 and 3 hours on top of this.
-ModTileCacheDurationMinimum 10800
-
-# Lower zoom levels are less likely to change noticeable, so these could be cached for longer
-# without users noticing much.
-# The heuristic offers three levels of zoom, Low, Medium and High, for which different minimum
-# cacheing times can be specified.
-
-#Specify the zoom level below which Medium starts and the time in seconds for which they can be cached
-ModTileCacheDurationMediumZoom 13 86400
-
-#Specify the zoom level below which Low starts and the time in seconds for which they can be cached
-ModTileCacheDurationLowZoom 9 518400
-
-# A further heuristic to determine cacheing times is when was the last time a tile has changed.
-# If it hasn't changed for a while, it is less likely to change in the immediate future, so the
-# tiles can be cached for longer.
-# For example, if the factor is 0.20 and the tile hasn't changed in the last 5 days, it can be cached
-# for up to one day without having to re-validate.
-ModTileCacheLastModifiedFactor 0.20
-
-## Tile Throttling
-## Tile scrappers can often download large numbers of tiles and overly staining tileserver resources
-## mod_tile therefore offers the ability to automatically throttle requests from ip addresses that have
-## requested a lot of tiles.
-## The mechanism uses a token bucket approach to shape traffic. I.e. there is an initial pool of n tiles
-## per ip that can be requested arbitrarily fast. After that this pool gets filled up at a constant rate
-## The algorithm has to metrics. One based on overall tiles served to an ip address and a second one based on
-## the number of requests to renderd / tirex to render a new tile.
-
-## Overall enable or disable tile throttling
-ModTileEnableTileThrottling Off
-## When the tileserver is behind a proxy one can use the X-Forwarded-For http header to determin the remote IP for throttling
-## 0: don't use X-Forwarded-For
-## 1: Use the first address in the X-Forwarded chain, which should be the client address. However, this may not be trusted.
-## 2: Use the last address in the X-Forwarded chain. If one uses a reverse proxy, this will be the IP address seen by the reverse proxy and can be trusted.
-ModTileEnableTileThrottlingXForward 0
-
-## Parameters (poolsize in tiles and topup rate in tiles per second) for throttling tile serving.
-ModTileThrottlingTiles 10000 1
-## Parameters (poolsize in tiles and topup rate in tiles per second) for throttling render requests.
-ModTileThrottlingRenders 128 0.2
-
- <Directory />
- Options FollowSymLinks
- AllowOverride None
- </Directory>
- <Directory /var/www/>
- Options Indexes FollowSymLinks MultiViews
- AllowOverride None
- Order allow,deny
- allow from all
- </Directory>
-
- ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
- <Directory "/usr/lib/cgi-bin">
- AllowOverride None
- Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
- Order allow,deny
- Allow from all
- </Directory>
-
- Alias /doc/ "/usr/share/doc/"
- <Directory "/usr/share/doc/">
- Options Indexes MultiViews FollowSymLinks
- AllowOverride None
- Order deny,allow
- Deny from all
- Allow from 127.0.0.0/255.0.0.0 ::1/128
- </Directory>
-
-</VirtualHost>
-
View it on GitLab: https://salsa.debian.org/debian-gis-team/libapache2-mod-tile/commit/0b44561a8ea2150016891cb929c2754dfdafd840
--
View it on GitLab: https://salsa.debian.org/debian-gis-team/libapache2-mod-tile/commit/0b44561a8ea2150016891cb929c2754dfdafd840
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-grass-devel/attachments/20190719/229663e3/attachment-0001.html>
More information about the Pkg-grass-devel
mailing list