index.rst 2.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. .. _community_azure_tilecache:
  2. GWC Azure BlobStore plugin
  3. ==========================
  4. This plugin supports the use of the `Azure BLOB storage <https://azure.microsoft.com/services/storage/blobs/>`_. as storage medium for :ref:`gwc_webadmin`.
  5. Installing the Azure BlobStore plugin
  6. -------------------------------------
  7. #. Download the extension from the `nightly GeoServer community module builds <https://build.geoserver.org/geoserver/main/community-latest/>`_.
  8. .. warning:: Make sure to match the version of the extension to the version of the GeoServer instance!
  9. #. Extract the contents of the archive into the ``WEB-INF/lib`` directory of the GeoServer installation.
  10. Configuring the Azure BlobStore plugin
  11. --------------------------------------
  12. Once the plugin has been installed, one or more Azure BlobStores may be configured through :ref:`gwc_webadmin_blobstores`.
  13. Afterwards, cached layers can be explicitly assigned to it or one blobstore could be marked as 'default' to use it for all unassigned layers.
  14. .. figure:: img/azureblobstore.png
  15. :align: center
  16. Container
  17. ~~~~~~~~~
  18. The name of the Azure storage container where the tiles are stored.
  19. Account name
  20. ~~~~~~~~~~~~
  21. Azure storage account name
  22. Account key
  23. ~~~~~~~~~~~
  24. Azure storage Account Key.
  25. Azure Object Key Prefix
  26. ~~~~~~~~~~~~~~~~~~~~~~~
  27. A prefix path to use as the root to store tiles under the container (optional).
  28. Maximum Connections
  29. ~~~~~~~~~~~~~~~~~~~
  30. The maximum number of allowed open HTTP connections.
  31. Use HTTPS
  32. ~~~~~~~~~
  33. When enabled, a HTTPS connection will be used. When disabled, a regular HTTP connection will be used.
  34. Proxy Host
  35. ~~~~~~~~~~
  36. Proxy host the client will connect through (optional).
  37. Proxy Port
  38. ~~~~~~~~~~
  39. Proxy port the client will connect through (optional).
  40. Proxy Username
  41. ~~~~~~~~~~~~~~
  42. User name the client will use if connecting through a proxy (optional).
  43. Proxy Password
  44. ~~~~~~~~~~~~~~
  45. Password the client will use if connecting through a proxy (optional).
  46. .. note::
  47. Unlike AWS, Azure storage controls whether tiles can be accessed by the public at the container level. If you desire to build a public tile cache
  48. that can be directly accessed by clients as static files, set the container access level to "public" or "BLOB" and fully seed the cache.