Set up Aggregate Analytics

Two short steps: connect a database here, then create your administrator account.

Server check: The server is ready.

PHP version (OK)
PHP 8.4.27 (8.2 or newer supported).
PHP extensions (OK)
All required extensions are enabled.
Database drivers (OK)
Available: MySQL or MariaDB, SQLite file.
Application files (OK)
Dependencies and dashboard assets are present.
Web root (OK)
Only the public folder is served.
Write access (OK)
PHP can write its configuration and data.

1. Confirm this is your server

Open accept.subschema.co/SETUP-CODE.txt with your hosting panel's file manager (it is next to README.md) and copy the code from it. This stops anyone else from finishing setup before you do.

Setup code

2. Connect a database

MySQL or MariaDB (MySQL 8.0 or MariaDB 10.6 or newer)
The usual choice on shared hosting. First create an empty database and a user with full access to it in your hosting panel.PostgreSQL (PostgreSQL 13 or newer)
Not available: PHP lacks the pdo_pgsql extension.Microsoft SQL Server (SQL Server 2017 or newer)
Not available: PHP lacks the pdo_sqlsrv extension.SQLite file (SQLite 3.25 or newer)
Nothing to create: the data is kept in var/data.db. Good for trying it out and small sites. BI tools read the whole file, so they cannot be limited to the reporting views.

Server

Usually localhost. Leave the port empty for the default.

Database name User name Password

Trust the server certificate (SQL Server only)

Needed when SQL Server uses a self-signed certificate, which is common on servers you run yourself. The connection is still encrypted.

Keep database connections open between requests (PostgreSQL only, recommended)

Each PHP worker reuses its connection instead of opening a new one for every page view, which more than doubled how much traffic a server handled in testing. Each worker holds one connection, so turn this off if your database host allows only a few connections.

Saving tests the connection, detects the server version and stores the settings, with a newly generated application secret, in .env.local.

Next: create the administrator account. The installation guide (also DEPLOYMENT.md in the application folder) describes this setup and links step-by-step guides for hosting panels.