Kordant/tasks/rebrand-to-kordant/02-update-database-connection-strings.md

02. Update Database Connection Strings and DB Names

meta: id: rebrand-to-kordant-02 feature: rebrand-to-kordant priority: P1 depends_on: [rebrand-to-kordant-01] tags: [infrastructure, database]

objective:

• Update all Turso database URLs and PostgreSQL connection strings from shieldai-* to kordant-* and database names from shieldai to kordant.

deliverables:

• web/src/server/db/index.ts — Turso URL updated
• web/drizzle.config.ts — Turso URL updated
• web/.env.development — DATABASE_URL updated
• web/.env.example — DATABASE_URL db name updated
• .env.example — DATABASE_URL user/db updated
• .github/workflows/ci.yml — PostgreSQL credentials and DB name updated

steps:

1. Edit web/src/server/db/index.ts — change libsql://shieldai-dev-* to libsql://kordant-dev-*
2. Edit web/drizzle.config.ts — same Turso URL update
3. Edit web/.env.development — same URL update
4. Edit web/.env.example — update .../shieldai postgres db name to .../kordant
5. Edit .env.example — update POSTGRES_DB: shieldai, POSTGRES_USER: shieldai, POSTGRES_PASSWORD: shieldai_dev, and pg_isready -U shieldai, and DATABASE_URL all to use kordant
6. Edit .github/workflows/ci.yml — update all shieldai references in db service config (POSTGRES_DB, POSTGRES_USER, POSTGRES_PASSWORD, pg_isready, DATABASE_URL)

tests:

• Unit: grep for any remaining shieldai.*turso.io patterns — should be zero
• Config: verify all DATABASE_URL references use kordant db name

acceptance_criteria:

• No shieldai-dev- or shieldai database name remains in any connection string
• CI workflow uses kordant as PostgreSQL database name

validation:

• Run grep -rn "libsql://shieldai" web/ — expect zero results
• Run grep -rn "POSTGRES_DB: shieldai" .github/ — expect zero results