Upstream/dynmap
1
0
Fork 0
mirror of https://github.com/webbukkit/dynmap.git synced 2024-11-28 13:15:30 +01:00
Code Issues Projects Releases Wiki Activity

Updated Storage Setup (markdown)

mikeprimm 2022-02-23 19:07:08 -06:00
parent 8def969b5e
commit 6125829d28
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Storage-Setup.md

@ -1,7 +1,7 @@
Dynmap required a large amount of storage for storing map tiles, markers and other map data. By default, this storage is simply provided by the local file system, but alternate storage technologies are supported. Currently, the supported storage technologies includes:
* [[File System Storage]] - this is the default, and simplest storage option
* [[MySQL/MariaDB Storage]] - this uses a MySQL or MariaDB SQL database for storing map data. This can offer some advantages - in particular, allowing the web server to be on a different computer/VM/container than that running the Minecraft server.
* [[PostgreSQL Storage]] - this uses a PostgreSQ SQL database for storing map data. This can offer some advantages - in particular, allowing the web server to be on a different computer/VM/container than that running the Minecraft server.
* [[SQLite Storage]] - this uses the simple SQlite SQL database for storing map data. This is relatively similar to the file system storage (it is local and in process with the Minecraft server), but offers some appeal in reducing the content of the map storage to be contained in one (huge) file
* [[AWS S3 Storage]] - this option offers both an alternative storage solution, and an external web serving solution, allowing the map data to be published to, and then served from, an AWS S3 'bucket', providing a convenient option for servers on hosting environments where the option for large local storage and/or the need for an additional TCP/IP port for the internal web server is a problem.
* [[File System Storage]] - this is the default, and simplest storage option
* [[MySQL/MariaDB Storage]] - this uses a MySQL or MariaDB SQL database for storing map data. This can offer some advantages - in particular, allowing the web server to be on a different computer/VM/container than that running the Minecraft server.
* [[PostgreSQL Storage]] - this uses a PostgreSQ SQL database for storing map data. This can offer some advantages - in particular, allowing the web server to be on a different computer/VM/container than that running the Minecraft server.
* [[SQLite Storage]] - this uses the simple SQlite SQL database for storing map data. This is relatively similar to the file system storage (it is local and in process with the Minecraft server), but offers some appeal in reducing the content of the map storage to be contained in one (huge) file
* [[AWS S3 Storage]] - this option offers both an alternative storage solution, and an external web serving solution, allowing the map data to be published to, and then served from, an AWS S3 'bucket', providing a convenient option for servers on hosting environments where the option for large local storage and/or the need for an additional TCP/IP port for the internal web server is a problem.