Two supported paths

Deploy on Wasmer, or run the same tree locally.

The application code uses Wasmer's managed DB_* variables when present and falls back to a local tabletime/config/db_config.php. This keeps the live deployment and conventional PHP/MySQL hosting on the same source tree.

Wasmer CLI · recommended for eski19758

The root app.yaml targets owner noah_king98, app eski19758, managed MySQL and the us-losa1 region. From the extracted package root:

wasmer login
wasmer deploy
wasmer app database list

Or run scripts/wasmer-deploy.sh on Linux/macOS or scripts/wasmer-deploy.ps1 in PowerShell. After deployment, check /health.php, then open /tabletime/setup.php. Initialization is offered only when the database has no Tabletime tables; after a successful first setup, the installer becomes status-only.

Local / ordinary PHP hosting

Create a MySQL/MariaDB database and user.
Copy app/tabletime/config/db_config.example.php to app/tabletime/config/db_config.php.
Edit host, port, database, username and password. The real file is ignored by Git.
Serve app/ as the document root. For a quick local test run scripts/local-dev.sh or scripts/local-dev.ps1.
Visit http://127.0.0.1:8080/tabletime/setup.php and initialize once.

Requirements: PHP 8.x with mysqli, plus MySQL/MariaDB. The local server script does not install those dependencies; it only starts PHP's built-in web server.

Storage behavior

Wasmer database

Tabletime treats roughly 100 MB as the database ceiling, prunes before the edge, and can refuse material writes if cleanup cannot keep usage below the guard.

Attachments

Post attachments are limited to 250 KB and live in MySQL so the same retention system accounts for them.

Site package

Software archives, the book, guides and historical migration bundles live with the website package and do not consume Tabletime's MySQL allowance.