<div dir="ltr">Hello,<div><br></div><div>we would like to use the feature in development above in a production environment.</div><div>Therefore it would be nice if the feature could make it into the next release of mapproxy once it is finished and tested.</div><div><br></div><div>Is there already any release schedule or are there other features to be released ? Would it be possible to be involved in the release planning ?</div><div><br></div><div>Best regards,</div><div>Moritz Kirmse</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 19, 2021 at 12:10 PM Moritz Kirmse <<a href="mailto:moritz.kirmse@camptocamp.com" target="_blank">moritz.kirmse@camptocamp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>I started work on this topic.</div><div>The basic functionality for refreshing existing tiles only is already implemented, but it cannot be configured.</div><div><br></div><div>in the (draft) PR below, I chose to introduce a command-line parameter for mapproxy-seed, --skip-uncached</div><div><a href="https://github.com/mapproxy/mapproxy/pull/515" target="_blank">https://github.com/mapproxy/mapproxy/pull/515</a><br></div><div>This seems more logical to me than including this parameter in the configuration file (as I had initially imagined with the parameter existing_tiles_only: True)</div><div><br></div><div>as for the second feature (keep_missing_files), everything already exists, it can be managed by the error handler in the mapproxy configuration with cache: False:</div><div><font face="monospace"><font color="#0b5394">sources:<br> my_source:<br> on_error:<br> other:<br> response: '#ff0000'<br> cache: False</font><br></font></div><div><br></div><div>best regards,</div><div>Moritz</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 6, 2021 at 5:11 PM Moritz Kirmse <<a href="mailto:moritz.kirmse@camptocamp.com" target="_blank">moritz.kirmse@camptocamp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>I am starting to develop a new feature for Mapproxy which is needed to get rid of some custom scripts, so that MapProxy can handle our whole tile caching workflow by its own.</div><div><br></div><div>We would like to add the following two features to the mapproxy-seed configuration:</div><div><br></div><div>- restriction of reseeding to existing tiles only, once they have become expired.<br>- conservation of old/stale tiles in case of missing replacement (source not available, for ex. http error).</div><div><br>This might be two non-default options under the 'refresh_before' tree in the seed.yaml file and look like in the example below:<br><br>seeds:<br> myseed1:<br> refresh_before:<br> weeks: 1<br> existing_tiles_only: True<br> keep_missing_files: True<br></div><div><br></div><div><br></div><div>I was about to create a Github issue for discussion on the topic, but it said issues are reserved to bugs and the mailing list shall be used for feature discussion.</div><div><br></div><div>So I will create a pull request and refine the feature there.</div><div><br></div><div>An existing PR will be useful for this feature, and I will be using it for development:</div><div><a href="https://github.com/mapproxy/mapproxy/pull/453" target="_blank">https://github.com/mapproxy/mapproxy/pull/453</a> (Added max-repeat param #453)<br></div><div><br></div><div>Do not hesitate to leave me any comments and suggestions, in case I overlooked something.</div><div><br></div><div>Best regards,</div><div>Moritz</div></div>
</blockquote></div>
</blockquote></div>