Storage and databases

Which one should you use

`storage.type`	Use it for
`sqlite`	One server. Everything goes in one file. Nothing to install, no password to set. The default, and the right answer for most servers.
`mysql`	A network that shares kits. Every server reads and writes the same database. MariaDB uses this type too. There is no separate `mariadb` type.
`postgresql`	A network that shares kits. Use it if you already run Postgres.
`redis`	A large network. Redis holds everything in memory, so reads and writes are fast.
`yml`	Testing only. A flat file.

Never use yml on a real server; concurrent writes lose data.

Set it up

Set storage.type, then fill the matching block.

SQLite
MySQL
PostgreSQL
Redis
YAML

config.yml

storage:
  type: sqlite

The file appears at plugins/PerPlayerKit/database.db.

config.yml

storage:
  type: mysql
  mysql:
    host: localhost
    port: '3306'
    dbname: kitdatabase
    username: username
    password: pa55w0rd
    use-ssl: false
    maximum-pool-size: 10

config.yml

storage:
  type: postgresql
  postgresql:
    host: localhost
    port: '5432'
    dbname: kitdatabase
    username: username
    password: pa55w0rd
    use-ssl: false
    maximum-pool-size: 10

config.yml

storage:
  type: redis
  redis:
    host: localhost
    port: 6379
    password: pa55w0rd

Data goes to plugins/PerPlayerKit/please-use-a-real-database.yml.

config.yml

storage:
  type: yml

Create the database before first start. The plugin creates its , not the database.

Set the same kits.max-slots on every server; a kit in slot 12 does not exist on a server capped at 9.

The last loaded inventory kit and enderchest slot are stored alongside kit data and read when players join. MySQL, PostgreSQL, and Redis can share these choices across servers. Keep public kit IDs and definitions consistent too. Kits are cached while a player is online; log them out before editing from another server.

Changing database later

Change database

SQLite to MySQL, or any two types.

Export and import

Copy a kit room to another server.

V3 storage type names ignore case and surrounding spaces. Unknown types stop startup. During an upgrade, an old SQLite fallback is preserved and reported; see Upgrading.

Start here

Features

Commands

Settings

Managing data

Common issues

For developers

Which one should you use

Set it up

Changing database later

Change database

Export and import

​Which one should you use

​Set it up

​Sharing one database across servers

​Changing database later

Change database

Export and import

Which one should you use

Set it up

Sharing one database across servers

Changing database later