Skip to content

Orca v0.62.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Oct 19:41
· 75 commits to main since this release
v0.62.0
90e7817

Databases

A project can now say in its orca.yaml which database it needs, and Orca provides it:

requires:
  database:
    engine: mysql
    version: ">=8.0"
    replaces: db

Orca gives the project a database and a user of its own, with a generated password, and writes the connection into its .env. The database comes from:

  1. your team's shared server, when the workspace has one for that engine and version;
  2. the project's own database service, when it has one and the workspace doesn't (as without Orca);
  3. a server Orca runs itself: MySQL, MariaDB or PostgreSQL, one per version, started the first time a project needs it.

With replaces:, the project's own database container doesn't start, and the connection is set on the services that used it, even when their compose file hardcodes it. Once a database exists, it stays on its server, so adding a shared server later never leaves data behind.

Shared servers for a team

A workspace shares servers with a databases: section naming services in its shared compose file. Each project gets its own database and user there, instead of every developer running a database container per project. The workspace file can choose per project with database: mysql or database: own.

The Databases page

A new Databases page shows every server and the databases on it, which project each is for, its user and size, and what each project requires (or why it can't be provided). For each database:

  • Connect: host, port, user and password, and a URL for TablePlus, DBeaver or DataGrip.
  • Snapshot and Restore: compressed SQL dumps on your computer, with a label such as before-migration.
  • Reset: empty it and run the project's seed command.

A project's database also shows on its stack page, on its card on the Workspace page and on the dashboard. Setting up a workspace project creates its database before the setup command runs, so migrations find it.

For AI tools

list_databases, database_connection, database_snapshot, database_restore and database_reset. Passwords never reach the AI tool, and restoring or resetting needs your approval. Ask "snapshot onecrm's database, then run the migration", and "restore it" if it goes wrong.

See Databases for everything.

Assets 16
Loading