maplibre/martin

Make the tile source cache configuration per source configurable

Open

#1,137 opened on Jan 17, 2024

View on GitHubContributor guide
 (3 comments) (3 reactions) (0 assignees)Rust (377 forks)auto 404
configgood first issuehelp wantedrustserving

Repository metrics

Stars
 (3,761 stars)
PR merge metrics
 (PR metrics pending)

Description

Each tile source cache should be configurable, at least to be able to selectively enable/disable cache, but possibly more advanced.

Steps:

  • Add a boolean or a tri-state enum to each tile source config to allow cache=enable|disable|auto. The auto setting (default) should be the same as enable for now, but may become more complex in the future.
  • Make cache configurable per source type (postgres vs mbtiles vs pmtiles)
  • For postgres, make cache configurable for all auto-discoverable tables / functions

Contributor guide

Research direction
Implement the configuration options for each tile source type, starting with a boolean or enum, then wire it through to cache behavior. Steps include adding a cache field to each source config, handling auto vs enable/disable, and special handling for Postgres auto discoverable tables.
Tech stack
rust
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rustbasic understanding of tile server configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65