69 Commits

Author	SHA1	Message	Date
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
Gan, Jimmy	2f65691e15	fix: use docker rm -f pattern from working claude-dev workflow ... Replicate the proven approach from deploy-claude-dev-dev.yml: - Use 'docker rm -f' to completely remove the old container - Let compose create a fresh container from scratch - Avoids the 'stop then recreate' flow that fails with network errors This works because Docker Compose handles initial network connection during 'up' differently than reconnection during recreate. The rm -f approach succeeds even from the workflow container context.	2026-04-04 02:05:09 +08:00
Gan, Jimmy	2a8e5d4952	fix: stop then up instead of force-recreate ... force-recreate still tries to disconnect/reconnect networks which fails. Use stop then up - compose will detect the image changed and recreate the container automatically without network issues.	2026-04-04 01:52:58 +08:00
Gan, Jimmy	e396f77299	fix: use --force-recreate to update container in-place ... This avoids disconnecting from networks which seems to cause issues when run from the workflow container. Force recreate updates the container without removing it first.	2026-04-04 01:36:18 +08:00
Gan, Jimmy	f27d414182	fix: cd to compose directory before running docker compose ... The workflow needs to be in the same directory as the compose file for docker compose to work properly. Manual execution worked, so replicate that approach.	2026-04-04 01:26:56 +08:00
Gan, Jimmy	f19b70d179	fix: use docker stop/rm instead of compose down for deploy ... docker compose down may have issues with external networks or project names. Use direct docker stop/rm commands instead.	2026-04-04 01:15:24 +08:00
Gan, Jimmy	e0cc38ecb5	fix: properly recreate container on deploy ... Use 'docker compose down' then 'up' instead of --no-recreate to ensure the new image is used and avoid network connection errors.	2026-04-04 00:45:55 +08:00
Gan, Jimmy	2c7787dced	revert: disable BuildKit due to slow performance on NAS ... BuildKit operations (load dockerfile, load context, FROM) are taking 20-80s each on the NAS due to filesystem/resource constraints. Legacy builder is faster. Keeping pip mirror optimization which provides the real speed improvement.	2026-04-04 00:27:39 +08:00
Gan, Jimmy	ee72a891d5	perf: optimize build speed with pip mirror and BuildKit	2026-04-04 00:19:43 +08:00
Gan, Jimmy	7a50c070e1	fix: remove duplicate docker.sock mount from deploy workflows	2026-04-03 23:49:45 +08:00
Gan, Jimmy	5e9fa2ba56	fix: add Docker socket mount to CI workflows ... - Add /var/run/docker.sock mount to deploy-dev and deploy workflows - Fixes docker build hanging indefinitely in CI - Docker commands need socket access to communicate with daemon	2026-04-03 23:14:54 +08:00
Gan, Jimmy	af5b4d8411	fix: use --no-recreate to avoid network issues, fallback to create if needed	2026-04-02 21:12:53 +08:00
Gan, Jimmy	f275e52843	fix: stop container before compose up to avoid network recreation issues	2026-04-02 10:29:31 +08:00
Gan, Jimmy	21d0cd9ff6	fix: simplify deploy to match production pattern - use idempotent docker compose up	2026-04-02 10:01:25 +08:00
Gan, Jimmy	e152de6fc8	fix: add --remove-orphans and remove force-recreate flag	2026-04-02 09:54:19 +08:00
Gan, Jimmy	b425613941	fix: use docker-compose down to clean up networks properly	2026-04-02 09:37:47 +08:00
Gan, Jimmy	d72b2acf02	fix: disconnect networks and force recreate container	2026-04-02 09:30:15 +08:00
Gan, Jimmy	09fdf5fd62	fix: stop and remove existing container before deploy to avoid network conflict	2026-04-02 09:24:19 +08:00
Gan, Jimmy	dba4880445	fix: set DOCKER_API_VERSION=1.43 for NAS daemon compatibility	2026-04-02 09:15:59 +08:00
Gan, Jimmy	7ad4095ad6	fix: add exit code validation to test workflow to properly fail on test failures	2026-03-31 19:03:53 +08:00
Gan, Jimmy	084148ed32	fix: add SECRET_KEY environment variable to test workflow	2026-03-31 15:30:55 +08:00
Gan, Jimmy	51c4cd1a4e	test: disable coverage and add timeouts to identify slow/hanging tests	2026-03-31 13:45:44 +08:00
Gan, Jimmy	c98db64f32	ci: add test output capture and display in workflow summary	2026-03-31 11:07:46 +08:00
Gan, Jimmy	c538dff773	fix: use ubuntu-latest runner label for test workflow	2026-03-30 12:40:02 +08:00
Gan, Jimmy	b1f0af75bb	ci: enable test workflow on dev branch	2026-03-30 11:27:36 +08:00
Gan, Jimmy	8431920d26	feat: add comprehensive unit and integration testing infrastructure ... - Backend: pytest with unit tests (auth, rbac, config) and integration tests (auth flow, docker, files) - Frontend: vitest with unit tests (api client) and component tests (login) - CI: Gitea Actions workflow for automated testing with coverage reports - Documentation: TESTING.md guide with setup, usage, and best practices - Coverage goals: 80%+ backend, 70%+ frontend	2026-03-30 11:11:39 +08:00
Gan, Jimmy	99b626eadc	fix: add 60s timeout to registry mirror pre-pull to prevent CI hang	2026-03-20 01:04:14 +08:00
Gan, Jimmy	61a3d0ae4b	fix: sync dashboard compose files during CI deploy ... Ensure dashboard deploy workflows copy tracked compose files into /nas-dashboard before docker compose up, so new SSH host mounts/envs (like Mac terminal) actually reach runtime. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-06 08:43:01 +08:00
Gan, Jimmy	c49d34210d	fix: remove stale claude-dev container before deploy ... Delete any existing claude-dev container before compose up so name conflicts do not block CI deployment. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-03 02:11:52 +08:00
Gan, Jimmy	b384b2f462	fix: ensure claude-dev runtime directory exists before snapshot ... Create /claude-dev-runtime before writing previous-image.txt so post-build record step does not fail when the bind path is absent. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-03 02:05:52 +08:00
Gan, Jimmy	cb2a842ab6	fix: remove slow server2 preload from claude-dev deploy workflow ... Drop the server2 preload stage and rely on direct docker build pulls to avoid long-running preload stream stalls in CI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-03 01:42:30 +08:00
Gan, Jimmy	a683321d92	fix: remove chmod on read-only mounted preload key ... Drop chmod on the read-only mounted server2 SSH key so preload can execute without failing the workflow before the SSH attempt. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-03 01:30:01 +08:00
Gan, Jimmy	d7b2cb3885	fix: mount SSH key for server2 preload in runner job ... Mount a read-only SSH key into the claude-dev deploy runner container and use it explicitly for server2 preload so the fast-path image transfer can authenticate. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-03 01:22:24 +08:00
Gan, Jimmy	8c23aabd97	fix: make claude-dev preload non-blocking in CI ... Treat server2 preload as best-effort so missing SSH keys do not fail deployment; fall back to normal registry pull during image build. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-03 01:02:06 +08:00
Gan, Jimmy	88c378594e	fix: use explicit server2 SSH target in claude-dev preload ... Replace the runner-only host alias with an explicit SSH user@host so the preload step can resolve and stream the base image tar reliably. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-03 00:59:00 +08:00