Schéma de la base de données — Référence développeur

Ce document décrit le schéma complet de la base de données gitrust, orienté développeur : types SeaORM côté Rust, enums, contraintes de modèle, et ordre des migrations.

Pour la vue admin (sauvegardes, supervision), consultez le manuel d’administration.

ERD — Diagramme entité-relation

erDiagram
    %% ===== Tables rustwarden-core =====
    users {
        uuid id PK
        string username UK
        string email UK
        string password_hash
        boolean must_change_password
        boolean email_verified
        timestamptz last_login_at
        timestamptz created_at
        timestamptz updated_at
    }

    resources {
        uuid id PK
        string resource_type
        uuid resource_id
        uuid owner_id FK
        boolean is_public
        timestamptz created_at
    }

    resource_shares {
        uuid id PK
        uuid resource_id FK
        uuid shared_with_user_id FK
        string permission_level
        uuid shared_by_user_id FK
        timestamptz created_at
    }

    user_totp {
        uuid id PK
        uuid user_id FK
        text encrypted_secret
        boolean enabled
        text backup_codes_json
        timestamptz enabled_at
        timestamptz created_at
        timestamptz updated_at
    }

    %% ===== Tables gitrust-core =====
    repositories {
        uuid id PK
        uuid owner_id FK
        string slug
        string description
        string disk_path
        string default_branch
        boolean is_empty
        timestamptz created_at
        timestamptz updated_at
    }

    ssh_keys {
        uuid id PK
        uuid user_id FK
        string title
        string fingerprint UK
        string key_type
        text key_data
        timestamptz last_used_at
        timestamptz created_at
    }

    teams {
        uuid id PK
        uuid owner_id FK
        string slug
        string description
        timestamptz created_at
        timestamptz updated_at
    }

    team_members {
        uuid id PK
        uuid team_id FK
        uuid user_id FK
        string role
        timestamptz created_at
    }

    team_repository_access {
        uuid id PK
        uuid team_id FK
        uuid repository_id FK
        string permission
        timestamptz created_at
    }

    personal_access_tokens {
        uuid id PK
        uuid user_id FK
        string name
        string token_hash UK
        string scopes
        timestamptz expires_at
        timestamptz last_used_at
        timestamptz created_at
    }

    issues {
        uuid id PK
        uuid repository_id FK
        integer number
        uuid author_id FK
        string title
        text body
        string state
        uuid closed_by FK
        timestamptz created_at
        timestamptz updated_at
    }

    issue_comments {
        uuid id PK
        uuid issue_id FK
        uuid author_id FK
        text body
        timestamptz created_at
        timestamptz updated_at
    }

    labels {
        uuid id PK
        uuid owner_id FK
        uuid repository_id FK
        string name
        string color
        string description
        string label_type
        timestamptz created_at
    }

    issue_labels {
        uuid id PK
        uuid issue_id FK
        uuid label_id FK
        timestamptz created_at
    }

    pull_requests {
        uuid id PK
        uuid repository_id FK
        integer number
        uuid author_id FK
        string title
        text body
        string source_branch
        string target_branch
        string state
        timestamptz merged_at
        uuid merged_by FK
        string merge_commit_sha
        timestamptz created_at
        timestamptz updated_at
    }

    pr_comments {
        uuid id PK
        uuid pull_request_id FK
        uuid author_id FK
        text body
        timestamptz created_at
    }

    import_jobs {
        uuid id PK
        uuid repository_id FK
        uuid owner_id FK
        text source_url
        text target_slug
        string status
        string phase
        int received_objects
        int total_objects
        bigint received_bytes
        text error_message
        timestamptz started_at
        timestamptz finished_at
        int duration_ms
        timestamptz created_at
        timestamptz updated_at
    }

    %% Relations
    users ||--o{ repositories : "possède"
    users ||--o{ ssh_keys : "enregistre"
    users ||--o{ teams : "crée"
    users ||--o{ resources : "possède"
    users ||--o| user_totp : "configure"
    repositories ||--o| resources : "enregistre dans"
    resources ||--o{ resource_shares : "partage"
    teams ||--o{ team_members : "contient"
    teams ||--o{ team_repository_access : "accède à"
    repositories ||--o{ team_repository_access : "accessible par"
    repositories ||--o{ issues : "contient"
    issues ||--o{ issue_comments : "a"
    issues ||--o{ issue_labels : "étiquetée"
    labels ||--o{ issue_labels : "appliquée"
    repositories ||--o{ pull_requests : "contient"
    pull_requests ||--o{ pr_comments : "a"
    users ||--o{ personal_access_tokens : "crée"
    users ||--o{ import_jobs : "lance"

Tables rustwarden-core (framework — read-only pour gitrust)

Ces tables sont gérées exclusivement par le framework rustwarden-core. Ne les modifiez jamais directement depuis gitrust.

Tables gitrust-core

repositories

Index : UNIQUE(owner_id, slug), INDEX(owner_id)

Lien ResourceService : chaque dépôt est enregistré dans resources avec resource_type = "repository" et resource_id = repositories.id.

ssh_keys

Validation : RSA ≥ 4096 bits obligatoire. Fingerprint calculé à l’insertion.

teams et team_members

personal_access_tokens

issues

labels

Index : UNIQUE(owner_id, repository_id, name, label_type)

pull_requests

import_jobs

Ordre des migrations

Toutes les migrations sont exécutées par AppMigrator (combine core + gitrust) dans gitrust_core::migrations::run_migrations().

Voir aussi

• Ajouter une migration DB
• Services API interne
• Modèle de permissions RBAC