DaX/Filamenteka
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
113 Commits 5 Branches 7 Tags
b24a1fea27baac49c43d31464dd1ceaf829d8663
Commit Graph

19 Commits

Author SHA1 Message Date
DaX
b24a1fea27 Diagnostic: find node binary path and working directory from running process
Some checks failed
Deploy / tag-deploy (push) Has been cancelled
Details
Deploy / deploy-frontend (push) Has been cancelled
Details
Deploy / detect (push) Successful in 4s
Details
Deploy / deploy-api (push) Failing after 28s
Details
2026-03-05 01:59:18 +01:00
DaX
93df263214 Diagnostic: check Docker, running services, and OS on EC2
Some checks failed
Deploy / detect (push) Successful in 6s
Details
Deploy / deploy-api (push) Failing after 30s
Details
Deploy / tag-deploy (push) Has been cancelled
Details
Deploy / deploy-frontend (push) Has been cancelled
Details
2026-03-05 01:57:57 +01:00
DaX
e50f361b07 Diagnostic: comprehensive node binary search without set -e
Some checks failed
Deploy / detect (push) Successful in 6s
Details
Deploy / deploy-api (push) Failing after 36s
Details
Deploy / tag-deploy (push) Has been cancelled
Details
Deploy / deploy-frontend (push) Has been cancelled
Details
2026-03-05 01:56:30 +01:00
DaX
9594ce56cb Diagnostic: find node binary and systemd service config on EC2
Some checks failed
Deploy / detect (push) Successful in 8s
Details
Deploy / deploy-api (push) Failing after 27s
Details
Deploy / tag-deploy (push) Has been cancelled
Details
Deploy / deploy-frontend (push) Has been cancelled
Details
2026-03-05 01:55:05 +01:00
DaX
11dbea3536 Fix migration: use find to locate node binary on EC2
Some checks failed
Deploy / detect (push) Successful in 7s
Details
Deploy / deploy-api (push) Failing after 26s
Details
Deploy / tag-deploy (push) Has been cancelled
Details
Deploy / deploy-frontend (push) Has been cancelled
Details
2026-03-05 01:53:17 +01:00
DaX
6d04e16cf6 Fix migration: use login shell to find node binary in SSM context
Some checks failed
Deploy / detect (push) Successful in 4s
Details
Deploy / deploy-api (push) Failing after 21s
Details
Deploy / tag-deploy (push) Has been cancelled
Details
Deploy / deploy-frontend (push) Has been cancelled
Details
2026-03-05 01:51:10 +01:00
DaX
85481512c8 Fix SSM parameter passing: use JSON files instead of inline parameters
Some checks failed
Deploy / detect (push) Successful in 4s
Details
Deploy / deploy-api (push) Failing after 22s
Details
Deploy / deploy-frontend (push) Successful in 2m3s
Details
Deploy / tag-deploy (push) Has been skipped
Details 
AWS CLI was misinterpreting inline --parameters with embedded paths.
Use file:// JSON parameters for all SSM commands to avoid shell quoting issues.
 2026-03-05 01:48:40 +01:00
DaX
1e95455139 Fix migration step: run node as ubuntu user for correct PATH
Some checks failed
Deploy / detect (push) Successful in 4s
Details
Deploy / deploy-api (push) Failing after 14s
Details
Deploy / deploy-frontend (push) Successful in 2m6s
Details
Deploy / tag-deploy (push) Has been skipped
Details 
SSM runs as root with minimal PATH. Use sudo -iu ubuntu to get the
ubuntu user's login shell environment where node is available.
 2026-03-05 01:46:16 +01:00
DaX
f929c384c1 Fix migration step: source nvm before running node on EC2
Some checks failed
Deploy / deploy-frontend (push) Successful in 2m5s
Details
Deploy / tag-deploy (push) Has been skipped
Details
Deploy / detect (push) Successful in 5s
Details
Deploy / deploy-api (push) Failing after 22s
Details 
SSM runs with minimal PATH that doesn't include nvm-managed node.
Source nvm.sh before executing migrate.js.
 2026-03-05 01:43:41 +01:00
DaX
291997caa5 Fix migration step: create api/ subdirectory and run migrate from project root
Some checks failed
Deploy / detect (push) Successful in 9s
Details
Deploy / tag-deploy (push) Has been cancelled
Details
Deploy / deploy-api (push) Failing after 26s
Details
Deploy / deploy-frontend (push) Has been cancelled
Details 
mkdir -p the api/ and database/ directories before copying files since EC2
only has server.js at the project root. Run migrate.js from project root
so dotenv picks up the .env file correctly.
 2026-03-05 01:42:01 +01:00
DaX
0741bd0d0e Fix tag-deploy condition to properly check individual job results
Some checks failed
Deploy / detect (push) Successful in 5s
Details
Deploy / deploy-api (push) Failing after 29s
Details
Deploy / tag-deploy (push) Has been cancelled
Details
Deploy / deploy-frontend (push) Has been cancelled
Details 
Use explicit job result checks instead of needs.*.result wildcard which
does not work in Gitea Actions. Prevent tagging when any deploy job fails.
 2026-03-05 01:40:03 +01:00
DaX
746f0925d0 Fix CI/CD pipeline: use archive download for migrations, inline SSM paths
All checks were successful
Deploy / tag-deploy (push) Successful in 4s
Details
Deploy / detect (push) Successful in 4s
Details
Deploy / deploy-api (push) Has been skipped
Details
Deploy / deploy-frontend (push) Successful in 2m5s
Details 
Replace complex Gitea API + python parsing in SSM with simple repo archive
download and extraction. Inline hardcoded paths in SSM commands instead of
shell variable expansion through single quotes to avoid quoting issues.
 2026-03-05 01:33:19 +01:00
DaX
2985ea4457 Rewrite CI/CD pipeline with deploy-tag change detection and verified deployments
Some checks failed
Deploy / detect (push) Successful in 4s
Details
Deploy / deploy-api (push) Failing after 22s
Details
Deploy / deploy-frontend (push) Successful in 2m5s
Details
Deploy / tag-deploy (push) Successful in 3s
Details 
Replace HEAD~1 diff with git tag-based change detection to catch all changes
since last successful deploy. Split into 4 parallel jobs: detect, frontend,
API (with migrations, health check, and rollback), and deploy tagging.
 2026-03-05 01:19:13 +01:00
DaX
a854fd5524 Upgrade to Next.js 16.1.6, React 19.2.4, and update all dependencies
All checks were successful
Deploy / deploy (push) Successful in 59s
Details 
- Next.js 15.5 → 16.1.6 (Turbopack default, faster builds)
- React/React-DOM 19.1 → 19.2.4
- @types/react 18 → 19, @types/react-dom 18 → 19
- TypeScript 5.2 → 5.9
- CI Node.js 18 → 20 (required by Next.js 16)
- Replace removed next lint with standalone ESLint config
- Auto-updated tsconfig.json (jsx: react-jsx, dev types)
 2026-02-16 02:39:22 +01:00
DaX
bd27f7a9e4 Fix pip3 install on Ubuntu runner with --break-system-packages flag
All checks were successful
Deploy / deploy (push) Successful in 1m18s
Details
2026-02-16 02:08:08 +01:00
DaX
145c2d4781 Optimize CI/CD pipeline for faster deploys
Some checks failed
Deploy / deploy (push) Failing after 1m12s
Details 
- Remove broken npm cache (was timing out ~5min per run)
- Replace AWS CLI v2 installer with pip3 install (~50MB less)
- Inline AWS credential config instead of separate action
- Merge steps to reduce overhead
 2026-02-16 02:04:38 +01:00
DaX
7cd2058613 Add AWS CLI install step to deploy workflow
All checks were successful
Deploy / deploy (push) Successful in 10m52s
Details 
Runner image doesn't include AWS CLI by default.
 2026-02-16 00:49:52 +01:00
DaX
c837af6015 Fix workflow: use env block instead of vars context
Some checks failed
Deploy / deploy (push) Failing after 5m59s
Details 
Gitea act runner doesn't resolve vars context properly.
Move all non-sensitive config to workflow-level env block.
 2026-02-16 00:43:13 +01:00
DaX
58c165749d Migrate from GitHub to Gitea with CI/CD
Some checks failed
Deploy / deploy (push) Failing after 6m11s
Details 
- Add Gitea Actions workflow for automated frontend and API deployment
- Update all raw download URLs from GitHub to Gitea
- Remove deprecated Amplify config and GitHub-specific Terraform variables
- Clean up commented-out Amplify resources from Terraform
- Update documentation to reflect new repository and CI/CD setup
 2026-02-16 00:35:08 +01:00