Configuration
Configure the selected application and backend rather than assumed global QQQ settings.
Configuration belongs to the application
QQQ metadata can be produced in Java and loaded from supported metadata files. A host defines its backends, authentication, server, scheduler, and environment lookup. There is no universal Spring-style application.yaml profile hierarchy or automatic QQQ_PORT/DATABASE_URL contract for every application.
Starter settings
The app starter configures MySQL through these environment values:
| Setting | Purpose |
|---|---|
| RDBMS_VENDOR | mysql for the starter schema |
| RDBMS_HOSTNAME | Database host |
| RDBMS_PORT | Database port |
| RDBMS_DATABASE_NAME | Dedicated database |
| RDBMS_USERNAME | Database user |
| RDBMS_PASSWORD | Database credential |
Use process environment variables or the starter's documented local .env mechanism. Keep credentials outside Git. The host and credentials must match the deployed database; validate a real query after startup.
Sample settings
The reference sample uses an in-memory H2 database. Its OAuth2 configuration uses OAUTH2_BASE_URL, OAUTH2_CLIENT_ID, OAUTH2_CLIENT_SECRET, and OAUTH2_SCOPES. Follow the sample README for the explicit local mock-auth option available in the selected revision.
For other applications, inspect the actual metadata provider and server entry point. See deployment and the QInstance reference.