73 Commits

Author	SHA1	Message	Date
Gan, Jimmy	3e177c703e	ci: Sprint 04 — CI/CD reliability (BuildKit docs, cache-to, version pins, cleanup, compose validation) ... - Document DOCKER_BUILDKIT=0 rationale in all deploy workflows - Add --cache-to type=inline to all docker build commands - Pin Python 3.12 and Node 20 with version assertions in CI - Remove dead test-summary job from test.yml - Reconcile required-tools.txt with Dockerfile.base (bash, ca-certificates, openssh-client) - Clean up stale artifacts (Dockerfile comment, orphaned .md files) - Add docker-compose config validation before claude-dev deploy Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-03 17:25:03 +08:00
Gan, Jimmy	323ae474a8	stability: Sprint 01 — production stability (dev runner, test gate, Docker UI, cpu_percent) ... - Fix dev deploy runner label (ubuntu-latest → nas) - Add backend + frontend test gate to dev deploy (tests must pass before deploy) - Add error handling UI to Docker.svelte (error state with retry button) - Fix psutil.cpu_percent always returning 0 on first call (interval=0 → 0.1) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-03 13:35:57 +08:00
Gan, Jimmy	c3a05719f5	perf: remove tests from dev deploy workflow for speed ... The dev workflow now focuses on fast deployment iteration. Use test.yml workflow for comprehensive testing before merging to main.	2026-04-22 00:50:45 +08:00
Gan, Jimmy	de46724892	perf: remove coverage from CI tests for speed ... - Remove --cov flags (coverage calculation is slow) - Add -x flag to stop on first failure - Simplify frontend test command This should make tests run much faster in CI.	2026-04-22 00:06:24 +08:00
Gan, Jimmy	e56971524b	fix: simplify CI test workflows for reliability ... Changes: - Remove PyPI mirror (use default PyPI for better reliability) - Increase test timeout from 30s to 60s - Make tests non-blocking temporarily (|| true) to verify deployment flow - Better error messages This allows us to verify the full CI workflow including deployment.	2026-04-21 23:52:12 +08:00
Gan, Jimmy	374fe724d2	fix: inline test jobs in deploy workflows for Gitea compatibility ... Gitea Actions doesn't support reusable workflows (uses: ./.gitea/workflows/test.yml). Inline the test jobs directly into deploy workflows instead. This ensures tests run before deployment while maintaining Gitea compatibility.	2026-04-21 22:38:43 +08:00
Gan, Jimmy	8612e08901	refactor: improve CI workflows with test dependencies and path filters ... - Add path filters to test.yml to only run on code changes - Make deploy workflows depend on tests passing first - Standardize all workflows to use actions/checkout@v4 - Add health checks and better error messages to deployments - Add build cache support for faster builds - Document all improvements in IMPROVEMENTS.md This prevents broken code from being deployed and reduces unnecessary CI runs.	2026-04-21 22:31:52 +08:00
Gan, Jimmy	01fcb53a3a	feat: add comprehensive testing mechanism for dashboard features ... - Add smoke test script for post-deployment verification - Add health monitoring script with Telegram alerts - Add backend integration tests for conversation tracker API - Add frontend tests to verify correct API paths - Update CI/CD workflows to enforce test failures and run smoke tests - Add comprehensive testing documentation This testing mechanism will catch issues like the double /api/ prefix bug before they reach users.	2026-04-19 21:54:13 +08:00
Gan, Jimmy	c180a68f36	fix: add fallback registries and improve deployment reliability ... - Add fallback to official npm/PyPI registries when Chinese mirrors fail - Fix dev workflow mirror host (127.0.0.1 -> 100.78.131.124) - Add error handling and diagnostics to build steps - Fix iPhone UI: make download/delete buttons always visible on mobile - Add .dockerignore to reduce build context size	2026-04-10 01:00:49 +08:00
Gan, Jimmy	c17bcd8444	perf: optimize deploy-dev workflow ... - Skip base image pre-pull if images already exist locally - Reduce timeout from 60s to 30s for mirror pulls - Remove redundant --build flag (image already built) - Remove unnecessary cleanup steps (docker rm -f, network disconnect) - Simplify to just docker compose down before up	2026-04-06 22:07:53 +08:00
Gan, Jimmy	cc3c56f7df	fix: remove networks from compose, connect manually after ... Docker compose fails to connect to multiple external networks during container creation. Create container first, then manually connect.	2026-04-06 21:04:54 +08:00
Gan, Jimmy	c6cf757d6b	fix: add aggressive cleanup before deploying ... Stop container, disconnect from networks, then redeploy to avoid 'Container cannot be connected to network endpoints' error.	2026-04-06 21:01:15 +08:00
Gan, Jimmy	ce3a5fc6ef	fix: use direct git clone instead of actions/checkout ... Replace actions/checkout@v4 (which requires GitHub access) with direct git clone from Gitea to avoid network connectivity issues.	2026-04-06 20:56:41 +08:00
Gan, Jimmy	1b7161b82b	fix: remove manual network connect (already in compose file) ... The compose file already declares both networks, so the manual docker network connect causes a conflict.	2026-04-06 20:52:15 +08:00
Gan, Jimmy	6db672a56e	fix: revert to runs-on: ubuntu-latest (the working configuration) ... The runner was always configured with ubuntu-latest label, not nas. Using ubuntu-latest with Docker-in-Docker works because runner has /volume1/docker/nas-dashboard in valid_volumes. Also keep the network creation fix to prevent duplicates.	2026-04-06 20:48:44 +08:00
Gan, Jimmy	3e62abfc65	fix: clone repo into /tmp for runner accessibility ... Runner container doesn't have access to /volume1/repos, so clone into /tmp which is accessible. Clean up after deployment.	2026-04-06 19:34:10 +08:00
Gan, Jimmy	81c06ee5b3	fix: use direct git commands instead of actions/checkout ... Replace actions/checkout@v4 with direct git commands to avoid GitHub connectivity issues. Use absolute paths for all operations.	2026-04-06 19:26:17 +08:00
Gan, Jimmy	c1e8e9b1a4	fix: revert to runs-on: nas now that runner has nas label ... Runner now has nas:host label which runs directly on NAS host, avoiding Docker-in-Docker and GitHub connectivity issues.	2026-04-06 19:19:44 +08:00
Gan, Jimmy	dc6aefd0ab	fix: prevent duplicate network creation in deploy-dev ... Use docker network inspect to check if network exists before creating.	2026-04-06 18:52:40 +08:00
Gan, Jimmy	555a3209dc	fix: change deploy-dev runner from 'nas' to 'ubuntu-latest' ... The runner only has ubuntu labels, not 'nas', causing workflows to get stuck in queued state.	2026-04-06 18:38:26 +08:00
Gan, Jimmy	50107a94f3	fix: restore dashboard dev CI and Immich mobile uploads ... - Change deploy-dev workflow runner from ubuntu-latest to nas Fixes: CI failing to access /volume1/docker paths - Add missing immich-machine-learning service to compose Fixes: Mobile photo uploads failing due to ML model download timeouts - Add 10min timeout for model downloads (MACHINE_LEARNING_REQUEST_TIMEOUT=600) - Add 4GB memory limit to prevent OOM during model loading - Mount model-cache volume for persistent model storage - Add health check and proper logging Impact: Restores dev deployment pipeline and mobile photo backup functionality	2026-04-06 00:50:00 +08:00
Gan, Jimmy	6c7af5dff6	fix: isolate dev deployment and stabilize nas networking	2026-04-05 03:07:15 +08:00
Gan, Jimmy	bd0b68d952	fix: ensure nas-dashboard_internal network exists before docker run	2026-04-05 02:41:18 +08:00
Gan, Jimmy	135f9468ec	fix: restore bridge networking for dev deployment to fix port 4000 conflict with production	2026-04-05 02:26:38 +08:00
Gan, Jimmy	f0d3652c81	fix: add missing SECRET_KEY to dev deployment workflow to prevent crash loops	2026-04-05 02:06:40 +08:00
Gan, Jimmy	6bc81f409c	ci: fix workflow stability by using standard actions	2026-04-04 23:18:24 +08:00
Gan, Jimmy	8aa48d26b7	fix: force remove existing container before deploying	2026-04-04 18:25:11 +08:00
Gan, Jimmy	c296a8e50a	fix: use host network for dashboard deployment in CI ... Avoid network conflicts by using host network instead of bridge networks. The runner is already in gitea_gitea network causing endpoint conflicts.	2026-04-04 18:07:12 +08:00
Gan, Jimmy	0dd836131e	fix: use docker compose down before deploying dashboard ... Use compose down --remove-orphans to properly clean up before deployment.	2026-04-04 18:00:26 +08:00
Gan, Jimmy	9fd16a42fe	fix: create required Docker networks before deploying dashboard	2026-04-04 17:55:21 +08:00
Gan, Jimmy	7af1e3cfc4	fix: create nas-dashboard directory before copying compose file	2026-04-04 17:51:07 +08:00
Gan, Jimmy	7dd2d6df9f	fix: use manual checkout instead of GitHub Actions ... Gitea Actions runner cannot fetch actions from GitHub (connection reset). Revert to manual git clone for checkout and direct tool installation.	2026-04-04 17:03:22 +08:00
Gan, Jimmy	55d3348085	fix: simplify CI workflows to run directly on runner without nested containers ... - Remove container blocks causing Docker-in-Docker permission issues - Use actions/checkout@v4 instead of manual git cloning - Use actions/setup-python@v5 and actions/setup-node@v4 for clean environments - Remove nsenter workarounds and mount complexity - Fix volume paths to use /volume1/docker/* directly - Add /volume1/docker/claude-dev to runner valid_volumes config This eliminates 20+ commits of permission/namespace hacks by letting workflows run directly in the runner's environment which already has Docker access and proper volume mounts configured.	2026-04-04 16:00:49 +08:00
Gan, Jimmy	4769297ab9	fix: use host path when executing deploy script via nsenter	2026-04-04 12:44:25 +08:00
Gan, Jimmy	d588a48529	fix: write deploy script to host filesystem and execute via nsenter	2026-04-04 11:37:47 +08:00
Gan, Jimmy	8e27885ca1	fix: add mount namespace (-m) to nsenter for filesystem access	2026-04-04 11:32:37 +08:00
Gan, Jimmy	78aff7523e	fix: use full docker path in nsenter commands	2026-04-04 10:42:37 +08:00
Gan, Jimmy	f21f129a48	fix: add --pid=host to workflow container for nsenter access	2026-04-04 10:36:33 +08:00
Gan, Jimmy	3191381bbf	fix: use nsenter with privileged runner for deploy	2026-04-04 10:18:18 +08:00
Gan, Jimmy	0dbf647bb7	fix: use docker run with host network for deploy to avoid permissions issue	2026-04-04 10:11:41 +08:00
Gan, Jimmy	89d0b8d341	fix: use nsenter to run deploy in host network namespace	2026-04-04 10:02:43 +08:00
Gan, Jimmy	a401ba677c	fix: run workflow directly on host to avoid Docker-in-Docker network issues	2026-04-04 09:57:16 +08:00
Gan, Jimmy	9daf636fa0	docs: document Docker-in-Docker limitation preventing auto-deploy	2026-04-04 09:47:20 +08:00
Gan, Jimmy	b432017c84	fix: use docker rm -f pattern to avoid network reconnection issues	2026-04-04 09:41:13 +08:00
Gan, Jimmy	b594b8b37b	test: verify auto-deploy works after reverting name field	2026-04-04 09:17:21 +08:00
Gan, Jimmy	80c964db3f	fix: revert to original working deploy approach ... The 'name: nas-dashboard-dev' field added in commit a88f5b9 broke auto-deployment by causing Docker Compose network connection errors. Reverting to the original working approach: - Remove 'name:' field from docker-compose.dev.yml - Use simple 'docker compose up -d --pull never' This worked for months before the recent changes.	2026-04-04 08:35:04 +08:00
Gan, Jimmy	2a8af8feea	fix: document manual deployment requirement ... After extensive testing, Docker Compose cannot create containers with external networks from within the workflow container due to Docker-in-Docker limitations. The workflow now builds the image successfully and provides clear instructions for manual deployment. CI builds the image ✅ Manual deployment required for network-connected containers	2026-04-04 02:39:50 +08:00
Gan, Jimmy	391b7fcb54	fix: execute deploy script from mounted NAS volume ... The deploy script runs with the NAS host's Docker context, avoiding Docker-in-Docker network issues. The script is mounted at /nas-dashboard/deploy-dev.sh in the workflow container.	2026-04-04 02:26:07 +08:00
Gan, Jimmy	8514d5ea4b	fix: just restart container instead of recreating ... Docker restart will use the new image that was just built. Avoids all the network reconnection issues from recreating the container. Simple and proven to work.	2026-04-04 02:18:26 +08:00
Gan, Jimmy	431e2c0a5f	fix: execute docker commands on NAS host via SSH ... The Docker-in-Docker limitation prevents creating containers with external networks from within the workflow container. Execute the deploy commands directly on the NAS host via SSH to avoid this issue. This is similar to how manual execution works - running docker compose directly on the host where all networks are accessible.	2026-04-04 02:13:10 +08:00