@justb4
To be honest, #MapProxy is poor choice for rendering with #Mapnik if you do not want to maintain your own fork of MapProxy. Without one of the many unmerged MapProxy patches, rendering performance will be poorer than possible.
Reason: MapProxy does not cache the Mapnik objects and therefore it initialises the map style on each request. This causes unnecessary Postgres queries.
@jakobmiksch

RT @FOSS_Academy
Spannende Schulungen der @FOSS_Academy rund um #OpenSource #Geospatial
https://foss-academy.com/termine/

#PostGIS #QGIS #Python #Mapbender #MapServer #GeoServer #MapProxy #OSM #GDI #FOSSGIS #OSGeo & mehr
Jetzt anmelden!
@WhereGroup_com

Finally, my #Mapproxy works but it is slow and the CPU of my server is at 100%. So I integrated my #QGIS Server (not Mapproxy) in my #Mapbender and activated tiling in the layerset. Now almost every label is broken but I integrated a getfeature tool. I think it's an appropriate compromise.
Learning how to build your own little #WMS and Web#GIS is an interesting experience.
#gischat

I am learning to use #Mapproxy for my projects. I want to cache my #QGIS Server. The first experiences were very frustrating:
1. #Python 2.7 was the default setting in my #Ubuntuserver -> config.py did not work: mod_wsgi not found
--> I found and solved that problem after a day.
2. I activated caching -> My changes were not visible: That's obvious. There were old tiles in the cache. It took me a few hours to realize that.
--> I deleted the cache.
I hope now #Mapproxy works. #gischat