rename(phase 1): CapaKraken → Nexus across code, UI, docs, CI (#61)
CI / Architecture Guardrails (push) Successful in 2m38s
CI / Assistant Split Regression (push) Successful in 3m33s
CI / Typecheck (push) Successful in 3m51s
CI / Lint (push) Successful in 5m2s
CI / E2E Tests (push) Has been cancelled
CI / Fresh-Linux Docker Deploy (push) Has been cancelled
CI / Release Images (push) Has been cancelled
CI / Build (push) Has been cancelled
CI / Unit Tests (push) Has been cancelled

rename(phase 1): CapaKraken → Nexus across code, UI, docs, CI (#61)

Co-authored-by: Hartmut Nörenberg <hn@hartmut-noerenberg.com>
Co-committed-by: Hartmut Nörenberg <hn@hartmut-noerenberg.com>
This commit was merged in pull request #61.
This commit is contained in:
2026-05-21 16:28:40 +02:00
committed by Hartmut
parent d9a7ec0338
commit b41c1d2501
943 changed files with 24548 additions and 16832 deletions
+7 -7
View File
@@ -19,14 +19,14 @@ echo "Postgres is ready."
CI=true pnpm install --frozen-lockfile
# Regenerate Prisma client (needed after bind-mount overlays the image layer)
pnpm --filter @capakraken/db db:generate
pnpm --filter @nexus/db db:generate
# Sync full schema to the DB first. The files under prisma/migrations/ are
# idempotent SUPPLEMENTS (see "IF NOT EXISTS" guards in each migration.sql);
# they assume the base tables already exist from a prior `db push`. On a
# fresh DB, migrate deploy alone would fail because the first incremental
# migration references "users" before it exists.
pnpm --filter @capakraken/db exec prisma db push --schema ./prisma/schema.prisma --accept-data-loss --skip-generate
pnpm --filter @nexus/db exec prisma db push --schema ./prisma/schema.prisma --accept-data-loss --skip-generate
# After db push the schema matches schema.prisma exactly, but the
# _prisma_migrations table is empty, which makes `migrate deploy` fail
@@ -35,17 +35,17 @@ pnpm --filter @capakraken/db exec prisma db push --schema ./prisma/schema.prisma
# supplements (IF NOT EXISTS guards), so marking-as-applied is safe.
for m in packages/db/prisma/migrations/*/; do
name=$(basename "$m")
pnpm --filter @capakraken/db exec prisma migrate resolve \
pnpm --filter @nexus/db exec prisma migrate resolve \
--applied "$name" --schema ./prisma/schema.prisma || true
done
# Run pending migrations so a fresh checkout picks up incremental additions
pnpm --filter @capakraken/db db:migrate:deploy
pnpm --filter @nexus/db db:migrate:deploy
pnpm check:exports
pnpm check:imports
repo_home="/tmp/capakraken-dev-home"
repo_home="/tmp/nexus-dev-home"
# Cross-platform stat: GNU stat uses -c, BSD/macOS stat uses -f
if stat -c '%u' /app >/dev/null 2>&1; then
@@ -65,8 +65,8 @@ chown -R "$repo_uid:$repo_gid" "$repo_home"
if command -v setpriv >/dev/null 2>&1; then
exec setpriv --reuid="$repo_uid" --regid="$repo_gid" --clear-groups \
env HOME="$repo_home" XDG_CONFIG_HOME="$repo_home/.config" \
pnpm --filter @capakraken/web exec next dev -H 0.0.0.0 -p 3100
pnpm --filter @nexus/web exec next dev -H 0.0.0.0 -p 3100
else
exec su -s /bin/sh "#${repo_uid}" -c \
"HOME='$repo_home' XDG_CONFIG_HOME='$repo_home/.config' pnpm --filter @capakraken/web exec next dev -H 0.0.0.0 -p 3100"
"HOME='$repo_home' XDG_CONFIG_HOME='$repo_home/.config' pnpm --filter @nexus/web exec next dev -H 0.0.0.0 -p 3100"
fi