MySQL

briq_run({
  recipe: "mysql",
  params: {
    "version": "8.4",
    "database": "app",
    "size": "small",
    "diskGb": 2
  },
  wait: true
})

curl -X POST https://api.briq.cloud/v1/briqs \
  -H "Authorization: Bearer $BRIQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "recipe": "mysql",
    "params": {
      "version": "8.4",
      "database": "app",
      "size": "small",
      "diskGb": 2
    },
    "wait": true
  }'
# → { "briqs": [{ "id": "bq_…", … }], "outputs": { "DATABASE_URL": "…" }, … }

# ... when done, for each briq id
curl -X DELETE https://api.briq.cloud/v1/briqs/<id> \
  -H "Authorization: Bearer $BRIQ_API_KEY"

When to use it

• Your app targets MySQL or MariaDB and migrations must be checked against the real dialect.
• A test suite expects a mysql:// DATABASE_URL.

Tips

• First boot is slow: MySQL initialises its data directory, so briq_run can take 30 to 60 seconds. Later starts are fast.
• Root only, with a generated password (MYSQL_ROOT_PASSWORD inside the briq). Create least-privilege users with briq_exec: sh -c 'mysql -uroot -p"$MYSQL_ROOT_PASSWORD" -e "create user …"'.
• Import a dump: briq_files_put it to /dump.sql, then briq_exec with sh -c 'mysql -uroot -p"$MYSQL_ROOT_PASSWORD" app < /dump.sql'.
• Connect from outside: briq_expose port 3306 with protocol: "mysql". The mysql CLI needs 8.1 or later and --tls-sni-servername. See Connect to a database from outside.
• Bigger dataset? The volume starts small: pass diskGb, e.g. params: { diskGb: 20 }. Set it when the briq is created, and it counts toward your plan's disk.