mirror/litebans-php
1
0
Fork 0
mirror of https://gitlab.com/ruany/litebans-php.git synced 2025-05-24 17:02:44 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update Installation

Ruan 2022-05-16 18:59:41 +00:00
parent 16e737646a
commit 4de0d7867a
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Installation.md

@ -5,16 +5,14 @@ This is the installation guide for the LiteBans web interface.
Minimum requirements:
- An existing website hosted on an existing domain
- A MySQL database (which must allow remote SQL, if used remotely)
- PHP 5.3+ with `pdo_mysql` and `intl` modules installed and enabled
- PHP 5.3 or above, with `intl` and `pdo_mysql` modules installed and enabled.
Recommended:
- PHP 8.1+
- PHP 8.1 or above
- MariaDB as database server (not Oracle MySQL)
The web interface cannot be directly hosted on Enjin, see [FAQ](https://gitlab.com/ruany/LiteBans/wikis/FAQ#enjin).
If you're using a web host's database, contact them to find out whether their database accepts remote connections. Most [web hosts](https://gitlab.com/ruany/LiteBans/-/wikis/MySQL-Errors#hosts) do not provide this for free plans.
## Install
Installation steps:
@ -82,6 +80,8 @@ Ensure that all of the paths are correct (client key, client certificate, and CA
Use the paths for the client key/certificate rather than the server key/certificate as these are two separate things.
## Troubleshooting
If you're using a web host's database, contact them to find out whether their database accepts remote connections. Most [web hosts](https://gitlab.com/ruany/LiteBans/-/wikis/MySQL-Errors#hosts) do not provide this for free plans.
If you get redirected to the wrong page when trying to access bans (e.g. Multicraft admin panel instead of the web interface):
- Set up different subdomains for each web installation you have, instead of putting everything on the same domain/subdomain.
- Also set up different virtual-hosts for everything that should be installed separately, if needed. Each web package should get its own directory to prevent conflicts.