... | ... | @@ -77,13 +77,13 @@ import: |
|
|
---
|
|
|
|
|
|
###### LiteBans
|
|
|
### Import from LiteBans (convert H2 -> MySQL)
|
|
|
1. Connect LiteBans to the new MySQL database which you want to use instead of the H2 database
|
|
|
2. `/litebans info` should state that LiteBans is connected to a MySQL database. If not, go back to step 1.
|
|
|
### Import from LiteBans (convert H2 -> MySQL/MariaDB)
|
|
|
1. Connect LiteBans to the new MySQL/MariaDB database which you want to use instead of the H2 database
|
|
|
2. `/litebans info` should state that LiteBans is connected to a MySQL/MariaDB database. If not, go back to step 1.
|
|
|
3. Set `from: litebans` in config.yml
|
|
|
4. Set `sqlite: true` -- with LiteBans only, this option implies H2 and not SQLite
|
|
|
5. Run `/litebans import start`
|
|
|
6. If you get a **Wrong user name or password** error, set `import_mysql_username` and `import_mysql_password` to the H2 user/password stored in `h2.yml`. Note: these options are for the origin (H2) database, not the target (MySQL) database. The target database is always what the plugin is currently connected to.
|
|
|
6. If you get a **Wrong user name or password** error, set `import_mysql_username` and `import_mysql_password` to the H2 user/password stored in `h2.yml`. Note: these options are for the origin (H2) database, not the target (MySQL/MariaDB) database. The target database is always what the plugin is currently connected to.
|
|
|
|
|
|
### Import from LiteBans (convert MySQL -> H2)
|
|
|
1. Connect LiteBans to the new H2 database which you want to use instead of the MySQL database
|
... | ... | |