root
4715353795
fix(ci): auto-discover reachable Portainer URL from job container
...
CI/CD Pipeline / Build & Deploy (pull_request) Successful in 19s
The act_runner on the QNAP creates an ephemeral docker bridge per job.
That network can't always reach the canonical PORTAINER_URL
(http://192.168.1.30:9000 ) — first deploy run failed with
'Failed to connect to 192.168.1.30 port 9000 after 130317 ms'.
New step 0 probes several candidate URLs (container's own IPs, default
gateways, then the secret value as fallback) against /api/status and
uses the first that returns 200. The reachable host is then reused for
the DELETE+CREATE calls and the smoke-test on :3001.
2026-07-10 11:19:55 +00:00
root
f152379882
fix(ci): add concurrency guard + PR trigger + workflow_dispatch
...
CI/CD Pipeline / Build & Deploy (pull_request) Successful in 22s
Apply the same concurrency pattern used in the python-project-template:
- cancel-in-progress: false prevents the shared act_runner from
cancelling in-progress steps when a new push lands
- pull_request trigger ensures PRs are validated before merge
- workflow_dispatch allows manual re-runs
2026-07-09 15:23:40 +00:00
21a63b6947
fix(ci): remove Portainer deployment step (runner network isolated)
CI/CD Pipeline / Build & Deploy (push) Successful in 23s
2026-05-11 13:49:10 +02:00
58f0a00d4c
fix(ci): use plain docker build instead of buildx (runner /dev/null issue)
CI/CD Pipeline / Build & Deploy (push) Failing after 17s
2026-05-11 13:33:30 +02:00
83845f4894
fix(ci): use exact WarrantyHub working pattern with Docker actions
CI/CD Pipeline / Build & Deploy (push) Failing after 36s
2026-05-11 13:14:46 +02:00
7e90812373
fix(ci): use GITEATOKEN secret name
CI/CD Pipeline / Build & Deploy (push) Failing after 15s
2026-05-11 13:13:41 +02:00
1037f6a4ed
fix(ci): add auth token to git clone + consolidate steps
CI/CD Pipeline / Build & Deploy (push) Failing after 16s
2026-05-11 13:13:12 +02:00
8176b0b09b
fix(ci): use plain docker + git instead of GitHub actions
CI/CD Pipeline / Build & Deploy (push) Failing after 28s
2026-05-11 13:09:48 +02:00
42873ad9cc
fix(ci): force image pull via Portainer API (stop + pull + start)
CI/CD Pipeline / Build & Deploy (push) Failing after 41s
2026-05-11 13:06:15 +02:00
35f3ba8767
fix: use exact working CI pattern from WarrantyHub
CI/CD Pipeline / Build & Deploy (push) Failing after 42s
2026-05-11 13:03:04 +02:00
47bf985a79
fix: use official Docker actions like WarrantyHub workflow
CI/CD Pipeline / Build & Deploy (push) Failing after 41s
2026-05-11 11:25:29 +02:00
8d85589f0c
fix: use direct Docker build to avoid runner filesystem issues
...
CI/CD Pipeline / Build & Deploy (push) Failing after 24s
Gitea Actions runner has filesystem mount issue preventing Node.js extraction.
Solution: Build entire image with Docker (includes Node) instead of setup-node action.
Simpler and more reliable - build happens inside container.
2026-05-11 09:32:53 +02:00
c31692bae0
fix: remove npm cache from Gitea Actions
...
CI/CD Pipeline / Build Astro Site (push) Failing after 22s
CI/CD Pipeline / Deploy to Portainer (push) Has been skipped
Gitea Actions may not support npm cache like GitHub Actions does.
Simplify to just node version.
2026-05-11 09:29:28 +02:00
cc7043148a
ci: add Gitea Actions CI/CD with Portainer deployment
...
CI/CD Pipeline / Build Astro Site (push) Failing after 1m8s
CI/CD Pipeline / Deploy to Portainer (push) Has been skipped
Add complete CI/CD pipeline:
- Gitea Actions workflow (build + deploy)
- Multi-stage Dockerfile (Node build + nginx serve)
- nginx config with SPA routing and cache headers
- docker-compose.yml for local testing
- .dockerignore to optimize build
Pipeline flow:
1. Build job: npm ci + npm build + upload artifact
2. Deploy job (main only): Docker build + push to registry + Portainer webhook
Requires Gitea secrets:
- DOCKER_USERNAME
- DOCKER_PASSWORD
- PORTAINER_WEBHOOK_URL
2026-05-11 09:23:29 +02:00
root
wh-leader