Commit Graph
6 Commits
Author SHA1 Message Date
Kayashov.SMandClaude Sonnet 5 5fb05d8bec Fix CI: use plain docker build/push instead of buildx
Build and Deploy / build-and-deploy (push) Successful in 4m37s
buildx runs its own BuildKit daemon with a separate insecure-registry
config that act-runner-docker-config doesn't reach, so the push failed
with "server gave HTTP response to HTTPS client" even though the image
built fine and login succeeded. The classic docker engine in the dind
runner already trusts this registry, so use it directly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-14 18:56:35 +04:00
Kayashov.SMandClaude Sonnet 5 12df47cf98 Fix CI: point at Gitea's actual insecure registry address
Build and Deploy / build-and-deploy (push) Failing after 4m23s
git.kayashov.keenetic.pro is the KeenDNS HTTPS proxy in front of Gitea's web
UI - its cert only covers one subdomain level and it doesn't route /v2/...
registry API traffic, so docker login got back the proxy's own 404 HTML page.
The real registry address is the NodePort 192.168.1.100:30008, already set as
insecure-registry in act-runner-docker-config (dind push) and
/etc/rancher/k3s/registries.yaml (containerd pull) - use that everywhere.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-14 18:48:04 +04:00
Kayashov.SM 57d32bb50c Fix CI: KUBE_CONFIG secret is base64-encoded, restore decode step
Build and Deploy / build-and-deploy (push) Failing after 40s
2026-09-14 18:25:44 +04:00
Kayashov.SMandClaude Sonnet 5 7946b7727b Fix CI: use actual user-level secret names
Build and Deploy / build-and-deploy (push) Failing after 40s
Workflow referenced GITEA_REGISTRY_USER/GITEA_REGISTRY_TOKEN/KUBECONFIG_DATA,
but the account's global secrets are named REGISTRY_USER/REGISTRY_TOKEN/
KUBE_CONFIG, so docker/login-action got empty credentials. Also drop the
base64 decode for KUBE_CONFIG since it's stored as plain kubeconfig YAML.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-14 18:25:21 +04:00
Kayashov.SMandClaude Sonnet 5 e530d37dab Fix CI: add Maven Wrapper so build-deploy doesn't need a preinstalled mvn
Build and Deploy / build-and-deploy (push) Failing after 1m57s
The Gitea Actions runner image has no system Maven (setup-node/setup-java
only install those tools, not Maven), so the pipeline failed at 'mvn:
command not found'. Switch the build step to ./mvnw and pin the wrapper's
line endings/executable bit via .gitattributes so it survives Windows
checkouts intact.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-14 18:11:54 +04:00
Kayashov.SMandClaude Sonnet 5 915be9100b Initial MVP: recommendarr recommendation service
Build and Deploy / build-and-deploy (push) Failing after 1m50s
Spring Boot 3.3 backend + React frontend bundled into one jar, Postgres via
Hibernate ddl-auto, Radarr/Sonarr/Jellyfin/Plex/TMDB integrations with
runtime-editable settings, webhook-driven batch recompute, and k8s/Gitea CI-CD
for deployment into the arr namespace on k3s.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-14 18:06:54 +04:00