NotAShelf
1df28f6049
I'm going to delete all migrations one of those days... Signed-off-by: NotAShelf <raf@notashelf.dev> Change-Id: I8e2e32118c2d85438a8b343614038eda6a6a6964 |
||
|---|---|---|
| .. | ||
| 001_initial_schema.sql | ||
| 002_add_build_system.sql | ||
| 003_production_features.sql | ||
| 004_build_outputs_and_deps.sql | ||
| 005_channels_remote_builders.sql | ||
| 006_hardening.sql | ||
| 007_branch_and_scheduling.sql | ||
| 008_user_management.sql | ||
| 009_builds_job_name_index.sql | ||
| 010_pull_request_support.sql | ||
| 011_jobset_states.sql | ||
| README.md | ||
Database Migrations
This directory contains SQL migrations for the FC database.
Migration Files
001_initial_schema.sql: Creates the core database schema including projects, jobsets, evaluations, builds, and related tables.
Running Migrations
The easiest way to run migrations is to use the vendored CLI, fc-migrate.
Packagers should vendor this crate if possible.
# Run all pending migrations
fc-migrate up postgresql://user:password@localhost/fc_ci
# Validate current schema
fc-migrate validate postgresql://user:password@localhost/fc_ci
# Create a new migration
fc-migrate create migration_name
TODO: add or generate schema overviews