Deployment

Package a QQQ application and configure its actual database, authentication, and server lifecycle.

Build the application

Use the application's Maven build. For qqq-app-starter:

Bash

mvn clean verify
java -jar target/qqq-app-starter-0.1-SNAPSHOT.jar

Follow the starter README for its MySQL schema and RDBMS environment settings. Its local dashboard is on port 8000. The starter is a learning application with anonymous authentication; configure production authentication and permissions before using real data.

Runtime configuration

Configuration keys belong to the application and chosen backend. The starter uses RDBMS_VENDOR, RDBMS_HOSTNAME, RDBMS_PORT, RDBMS_DATABASE_NAME, RDBMS_USERNAME, and RDBMS_PASSWORD. A generic DATABASE_URL or QQQ_AUTH_SECRET is not an automatic framework contract.

For containers, provide your application JAR, a compatible Java runtime, configuration, and a startup command. Dockerfiles and Kubernetes manifests are application deliverables; QQQ does not generate them just because a module is present.

Verify production behavior

Verify the exact packaged artifact, database connectivity, authenticated and denied requests, scheduler startup, shutdown, and health probes. Configure the actual probe routes exposed by your server; do not assume /health/ready and /health/live exist. Test backup restoration and rollback before an upgrade that changes persistent data.

qRun managed hosting is a separate product preview, not a prerequisite or included service for QQQ 4.0.