This is a guide I wrote for Immich’s documentation. It features some Immich specific parts, but should be quite easy to adapt to other use cases.

It is also possible (and not technically hard) to self-host a protomaps release, but this would require 100GB+ of disk space (which I can’t spare right now). The main advantages of this guide over hosting a full tile server are :

  • it’s a single nginx config file to deploy
  • it saves you some storage space since you’re only hosting tiles you’ve previously viewed. You can also tweak the maximum cache size to your needs
  • it is easy to configure a trade-off between map freshness and privacy by tweaking the cache expiration delay

If you try to follow it, please send me some feedback on the content and the wording, so I can improve it

    • pcouy@lemmy.pierre-couy.frOP
      link
      fedilink
      arrow-up
      4
      ·
      4 months ago

      There have been some changes in a few recent releases related to the concerns I raised :

      • the default tile provider is now hosted by the Immich’s team using protomaps (still uses vloudflare though)
      • a new onboarding step providing the option to disable the map feature and clarifying the implications of leaving it enabled has been added
      • the documentation has been updated to clarify how to change the map provider, and includes this guide as a community guide