Commit Graph

22 Commits

Author SHA1 Message Date
Antigravity
bbe54cf656 fix: force recreate postgres with pgvector before app startup in deploy pipeline
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 5s
2026-05-12 07:46:07 +00:00
Antigravity
dc4244f2ad fix: pgvector deployment — idempotent migration, pgvector image, schema sync
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 2m21s
- docker-compose.yml: switch postgres:16-alpine to pgvector/pgvector:pg16
- migration: rewrite with IF NOT EXISTS guards, DO block for safe
  text→vector(1536) conversion, handles partial/re-run states
- schema.prisma (both): add @default(now()) on NoteEmbedding.updatedAt,
  sync mcp-server embedding type to Unsupported("vector(1536)")
- deploy.yaml: add docker compose pull postgres before build
2026-05-12 07:28:03 +00:00
Antigravity
98e246e257 fix: force git reset on deploy + toast persistant de génération
Some checks failed
Deploy to Production / Build and Deploy (push) Failing after 23s
- Remplace git pull par git fetch + git reset --hard origin/main dans
  le workflow CI pour éviter les conflits avec les fichiers locaux
- Ajoute un toast Sonner persistant (duration: Infinity) dès le clic sur
  Générer, qui survit à la navigation et se met à jour en succès/erreur
  avec action directe (Télécharger / Ouvrir)

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-05 21:15:38 +00:00
bc3577a388 ci: add mcp-server build to deploy pipeline
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 20s
The pipeline only built memento-note, causing mcp-server to run with
stale code/schema after pushes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-04-26 14:51:37 +02:00
434bb3ad71 fix: use prisma db push in entrypoint instead of migrate deploy
Some checks failed
Deploy to Production / Build and Deploy (push) Has been cancelled
The app uses db push (no migration files), so migrate deploy was a no-op.
Also removes the redundant migration step from deploy.yaml since the
entrypoint now handles schema sync on every container start.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-04-26 11:06:07 +02:00
88d7bc8b24 ci: add automatic prisma db push to deploy pipeline
Some checks failed
Deploy to Production / Build and Deploy (push) Has been cancelled
Run database migration after build and before container startup
so schema changes are always applied before the app goes live.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-04-26 10:53:31 +02:00
70a9e070fc ci: fix upsert - remove all occurrences before adding to prevent duplicates
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 4s
Made-with: Cursor
2026-04-25 23:00:19 +02:00
99ac686ac0 fix: pass full config to sendViaResend, force-recreate container after env update
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 39s
Made-with: Cursor
2026-04-25 22:48:05 +02:00
266551e82b ci: fix heredoc typo ENVSSH → ENDSSH
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 39s
Made-with: Cursor
2026-04-25 22:41:50 +02:00
f1097f76b0 ci: manage all .env.docker vars from Gitea variables & secrets
Some checks failed
Deploy to Production / Build and Deploy (push) Failing after 2s
Made-with: Cursor
2026-04-25 22:25:22 +02:00
8d8b9cde85 ci: add workflow_dispatch for manual trigger
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 4s
Made-with: Cursor
2026-04-25 22:06:42 +02:00
716e15c0b7 ci: update NEXTAUTH_URL and ADMIN_EMAIL from Gitea vars on deploy
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 4s
Made-with: Cursor
2026-04-25 22:03:42 +02:00
8aefedcaee ci: check port 80 (via Nginx) instead of 3000
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 4s
Made-with: Cursor
2026-04-25 21:54:28 +02:00
5bf2d7b983 ci: check http://192.168.1.190:3000 from runner, fix healthcheck node http
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 4s
Made-with: Cursor
2026-04-25 21:51:41 +02:00
4e84b03575 ci: fix healthcheck (use wget), increase timeout to 180s
Some checks failed
Deploy to Production / Build and Deploy (push) Failing after 3m13s
Made-with: Cursor
2026-04-25 21:44:09 +02:00
3944f699bd ci: fix git safe.directory for /opt/memento
Some checks failed
Deploy to Production / Build and Deploy (push) Failing after 3m51s
Made-with: Cursor
2026-04-25 21:16:22 +02:00
01d36a5956 ci: remove rsync, use git pull via SSH instead
Some checks failed
Deploy to Production / Build and Deploy (push) Failing after 2s
Made-with: Cursor
2026-04-25 21:10:00 +02:00
5915bd567c ci: fix runner label to ubuntu-24.04, deploy via SSH to 192.168.1.190
Some checks failed
Deploy to Production / Build and Deploy (push) Failing after 47s
Made-with: Cursor
2026-04-25 20:59:35 +02:00
acb784edbb ci: fix deploy workflow - use GITHUB_WORKSPACE env var and robust healthcheck
Some checks failed
Deploy to Production / Build and Deploy (push) Has been cancelled
Made-with: Cursor
2026-04-25 20:51:35 +02:00
Sepehr Ramezani
0c743ee679 ci: install runner on target server, eliminate SSH complexity
Some checks failed
Deploy to Production / Build and Deploy (push) Has been cancelled
Better architecture: act_runner runs directly on 192.168.1.190.
- No SSH keys needed, no secrets to configure in Gitea
- Runner executes docker compose commands locally
- Workflow uses rsync + docker compose build + healthcheck
- Updated DEPLOY.md with complete step-by-step guide

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-04-21 23:10:48 +02:00
Sepehr Ramezani
f3b58b32fd ci: add deploy script and simplify CI/CD workflow
Some checks failed
Deploy to Production / Deploy to 192.168.1.190 (push) Has been cancelled
- scripts/deploy.sh: automated deployment with interactive env setup
  (--env-only, --build, --full)
- Supports OpenRouter, OpenAI, Ollama, DeepSeek providers
- Auto-generates NEXTAUTH_SECRET and postgres password
- Waits for healthchecks, initializes DB, shows status
- CI/CD workflow simplified to call deploy.sh --build

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-04-21 22:55:15 +02:00
Sepehr Ramezani
106dac9ca4 ci: add Gitea Actions workflow for auto-deploy on push to main
Some checks failed
Deploy to Production / Deploy to 192.168.1.190 (push) Has been cancelled
SSH-based deployment to 192.168.1.190 via Gitea Runner.
Builds Docker images and restarts containers automatically.

Required Gitea secrets: DEPLOY_HOST, DEPLOY_USER, DEPLOY_SSH_KEY, DEPLOY_PATH

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-04-21 22:34:18 +02:00