Commit Graph

4 Commits

Author SHA1 Message Date
Дмитрий 14c98c37c2 fix(ci/deploy): drop ON CONFLICT on migrations marker INSERT (table has no UNIQUE)
Run 26566803068 created project_routing_snapshots successfully on prod (CREATE TABLE
+ partitions + RLS + GRANTs all committed). Marker INSERT into migrations table
failed: "there is no unique or exclusion constraint matching the ON CONFLICT specification"
because Laravel's migrations table has no UNIQUE on `migration` column.

Replaced with INSERT...SELECT WHERE NOT EXISTS for idempotency.

Table is now LIVE on prod — next workflow run will skip the CREATE block (TABLE_EXISTS
check passes) and go straight to the now-fixed marker INSERT.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-28 12:38:52 +03:00
Дмитрий 54360d6f3b fix(ci/deploy): pre-apply partitioned migrations via postgres superuser + e2e CWD fix
Workflow run 26564909645 failed: migration 2026_05_27_120000_create_project_routing_snapshots_table
hit 'SET ROLE crm_migrator' failure (pgsql conn = crm_app_user, not member of crm_migrator).
Failed SET ROLE poisoned transaction → subsequent CREATE TABLE failed SQLSTATE[25P02].

Fix in deploy.yml:
  New step 'Pre-apply partitioned migrations via postgres superuser' runs CREATE TABLE
  + indexes + RLS + GRANTs + partitions + system_settings insert via sudo -u postgres psql,
  then marks migration as ran in migrations table. Idempotent (checks both migrations
  table AND information_schema). Established prod pattern (memory: paused_at migration 26.05).

Side fix in tools/enforce-override-limit.test.mjs:
  CLI e2e tests used 'node tools/enforce-override-limit.mjs' without cwd, failed when
  vitest ran from app/. Added cwd: projectRoot via fileURLToPath(import.meta.url).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-28 12:33:47 +03:00
Дмитрий 81f92ca361 fix(ci/deploy): npm ci --legacy-peer-deps + Node 22 (deploy.yml v1.1)
Workflow run 26564332893 failed at 14s — most likely npm ci hit Histoire/Vite
peerDep conflict (quirk #74 in feedback_environment.md). --legacy-peer-deps
mirrors local install pattern. Also bumped to Node 22 (Node 20 actions deprecated).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-28 11:45:23 +03:00
Дмитрий 7511f4e537 feat(ci): GitHub Actions deploy workflow for liderra.ru — fundamental fix for dev→prod SSH block
Adds .github/workflows/deploy.yml — manual workflow_dispatch trigger that:
  1) checkouts requested ref (default main)
  2) builds frontend (npm ci + npm run build)
  3) tarballs app + db excluding .env/storage/vendor/node_modules/bootstrap-cache
  4) ssh-deploys via stored secret LIDERRA_SSH_KEY to ubuntu@111.88.246.137
  5) extracts overlay + runs /var/www/liderra/redeploy.sh (composer + migrate + restart)
  6) backfills today's snapshot (slepok-stage-2 Task 2.12 Step 3)
  7) runs smoke tests (migrate:status, snapshots count, service health, portal http)

Why this is needed:
  My dev VM (89.144.17.119) → prod VM (111.88.246.137) traffic
  passes TCP-handshake but app-layer banner exchange times out.
  Same VPC, SG 0.0.0.0/0, iptables empty, fail2ban clean — drop happens
  on YC backbone between specific source/dest pair.
  GitHub Actions runners come from Azure IPs, NOT affected by this filter.

One-time setup needed:
  GitHub Settings → Secrets → Actions → New secret
  Name: LIDERRA_SSH_KEY
  Value: content of ~/.ssh/liderra_deploy (private key, full file)

Future deploys: `gh workflow run deploy.yml -f ref=main` from anywhere.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-28 11:34:07 +03:00