Requirements
Qorekit is built for ordinary shared hosting. It needs no Redis, no websockets and no processes that keep running: queues and sessions use the database, and scheduled work runs from cron.
Server
| Needed | |
|---|---|
| PHP | 8.3 or newer |
| Database | MySQL 5.7 or newer, MariaDB 10.4 or newer, or PostgreSQL 13 or newer |
| Web server | Apache or LiteSpeed (with .htaccess), or nginx |
| Disk | About 30 MB for Qorekit (twice that for a week after an update, while the previous version is kept), plus your uploaded files |
Qorekit is tested on MySQL 8.4, MariaDB 11.4 and PostgreSQL 17.
PHP extensions
Required: ctype, curl, dom, fileinfo, filter, mbstring, openssl, pdo, session, tokenizer, xml, and pdo_mysql or pdo_pgsql for your database.
Recommended:
| Extension | Used for |
|---|---|
zip | Updating from within Qorekit |
sodium | Checking the signature of updates |
gd | Image previews |
intl | Better date and number formatting |
Most hosting panels let you turn extensions on yourself, under Select PHP version or PHP settings. The installer checks all of this before it starts, and says what is missing.
Write permissions
The web server must be able to write to:
storage/andbootstrap/cache/, always;- Qorekit's own folder, to write
.envduring installation and to put new files in place when updating.
On shared hosting this is usually already so.
A database of its own
Give Qorekit an empty database. If it must share a database with another program, set a table prefix during installation, such as qk_, so that its tables never collide with the other program's.
The database user needs the right to create, change and drop tables, since Qorekit creates a table for every entity you build.