532 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Gan, Jimmy	3942a344c7	fix: handle missing static directory gracefully for tests	2026-04-04 13:31:32 +08:00
Gan, Jimmy	0cfb1a6b5d	fix: create dummy static directory for backend tests	2026-04-04 13:23:18 +08:00
Gan, Jimmy	b48cbeb4c7	fix: regenerate package-lock.json to fix npm ci in tests	2026-04-04 13:22:18 +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	07eaec344a	test: final verification of auto-deploy	2026-04-04 11:02:24 +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	593863b28a	test: trigger deploy workflow to verify auto-deploy	2026-04-04 09:25:42 +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	0710b56feb	test: trigger deploy with updated script paths	2026-04-04 02:32:24 +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	42f87a526d	test: verify force-recreate deploy works	2026-04-04 01:46:02 +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	a88f5b9c95	fix: set explicit project name for dev compose to avoid conflicts ... The dev compose was inheriting 'nas-dashboard' project name, causing conflicts with the production dashboard when trying to use the same networks.	2026-04-04 01:07:03 +08:00
Gan, Jimmy	cf56c095bf	test: trigger deploy after removing stale container	2026-04-04 00:54:08 +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	85649745a2	test: trigger deploy after fixing duplicate mount issue	2026-04-04 00:14:31 +08:00
Gan, Jimmy	7a50c070e1	fix: remove duplicate docker.sock mount from deploy workflows	2026-04-03 23:49:45 +08:00
Gan, Jimmy	363e1e12d5	test: verify deploy workflow after runner restart	2026-04-03 23:46:40 +08:00
Gan, Jimmy	c5d40c9deb	test: verify CI after Gitea restart	2026-04-03 23:34:52 +08:00
Gan, Jimmy	7433b346fa	test: verify CI fix works	2026-04-03 23:31:23 +08:00
Gan, Jimmy	4e867d1d75	test: trigger CI deploy workflow	2026-04-03 23:23:26 +08:00
Gan, Jimmy	b15ed57425	chore: trigger deploy workflow to test CI fix	2026-04-03 23:17:25 +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	0e1612ff55	chore: trigger CI for OPC fixes	2026-04-03 22:55:21 +08:00
Gan, Jimmy	5da2ae01a0	fix: complete OPC system implementation ... - Add database connection retry logic (3 attempts, 5s delay) - Add missing database functions: get_task_by_id, get_agent_execution, approve_agent_execution, update_agent_config, update_execution_status - Complete agent execution approval workflow - Fix agent executor to handle approved executions - Fix inefficient task queries (use direct ID lookup) - Add error action handling in agent executor - Improve LiteLLM error handling with specific exception types - Reduce LiteLLM timeout from 60s to 30s - Fix execution status update to only set started_at once - Consolidate WebSocket datetime serialization with helper function - Implement update agent endpoint	2026-04-03 22:30:51 +08:00
Gan, Jimmy	a42e3d3050	fix: update agent seed data to use cc-kiro model	2026-04-03 00:00:44 +08:00
Gan, Jimmy	4c6bbd974a	fix: use simple 'anything' key for LiteLLM in dev	2026-04-02 23:52:57 +08:00
Gan, Jimmy	c945dfff5e	fix: use simple master key for LiteLLM auth	2026-04-02 23:47:38 +08:00
Gan, Jimmy	eee47fb967	fix: disable LiteLLM spend logs to avoid auth requirement	2026-04-02 23:46:23 +08:00
Gan, Jimmy	31b8e990b9	fix: disable LiteLLM auth for internal network use	2026-04-02 23:42:16 +08:00
Gan, Jimmy	e87a51cbc7	feat: add cc-kiro model with User-Agent header to bypass blocking	2026-04-02 23:25:55 +08:00