29 Commits
Author SHA1 Message Date
hermesandadmin 0a9e795b8f feat(hermes_infra/gitea): add second act_runner on rudolf-T (#53)
Closes #52.

Adds exactly one second act_runner on `rudolf-T`. The existing runner is constrained away from `rudolf-T`, so when that node is unavailable only the existing runner remains available. Both runners share the normal build label.

Validation: `docker stack config -c poc/gitea/stack-compose.yml` passes; the stack contains exactly two runner services.
Co-authored-by: rudolf <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13@gmail.com>
Co-authored-by: admin <rudolfss13@gmail.com>
Reviewed-on: #53
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-10-08 22:04:58 +02:00
hermesandalex 7e69577609 infra(hermes_squid/gitea): bump gitea 1.27.0 → 1.27.3 (#37)
## Summary

Bumps the Gitea stack image from `1.27.0` to `1.27.3` — the last stable release on the 1.27.x line.

This is the first PR in a two-step plan tracked in admin/brencher#63:

1. **This PR** — bump to `1.27.3`. Stable, security patches only, no schema change, no Projects API yet. Goal: validate the upgrade path (DB migration, container swap, compose-version label update) without introducing new features.
2. **Follow-up PR (planned)** — bump to `1.28.0` (or build from `main`) once `1.28.x` ships with the Projects REST API landed in `7fae3d5db` (merged 2026-08-08).

## Why 1.27.0 is insufficient

Gitea `1.27.0` was released 2026-07-13. Three weeks later, on 2026-08-08, `silverwind` merged PR go-gitea/gitea#38691 — the long-awaited Projects REST API (the resolution of go-gitea/gitea#14299, originally filed in 2019). That commit (`7fae3d5db`) added full CRUD for repo/org/user project boards, columns, and issue↔column assignment.

1.27.0 ships **before** that merge. Confirmed:
- `git ls-tree v1.27.0 --name-only | grep routers/api/v1/.*project` → empty.
- `git ls-tree 7fae3d5db --name-only | grep project` → `routers/api/v1/shared/project.go`, `routers/api/v1/swagger/project.go`, and routes registered inside `routers/api/v1/api.go` (`addProjectRoutes`).

The current prod instance at `gitea.rudolf.keenetic.link` reports `1.27.0`, which is why we cannot move kanban cards programmatically today (verified end-to-end in admin/brencher#63's repro section).

## Why stop at 1.27.3 (not jump straight to 1.28.0)

1.27.3 is the last stable 1.27.x and contains the SECURITY fix for CVE-2024-45337 (access-token scope bypass) plus 8 months of bug fixes — strictly safer than staying on 1.27.0.

1.28.0 is not yet released as of writing (only `v1.28.0-dev` exists on the upstream tag list, dated 2026-06-29 — before the Projects API merge). Going to `:dev` or `:main` would require a build pipeline we don't have today and would skip the version bump validation path. The Projects API change also adds a column to `project_board` (per #37701 migration `v333`), so the jump is a real schema change that should be its own validated step.

## Diff

```
-    image: docker.gitea.com/gitea:1.27.0
+    image: docker.gitea.com/gitea:1.27.3
```

## Validation after deploy

| Check | Expected |
|-------|----------|
| `GET /api/v1/version` | `1.27.3` |
| `POST /api/v1/repos/{owner}/{repo}/issues` | `201` |
| `PATCH /api/v1/repos/{owner}/{repo}/issues/{idx} {"projects":[id]}` | `200` with updated projects |
| WebSocket /ws uptime (admin/brencher#58 regression check) | no new KeyError |
| Stack `gitea_server` compose-version label | `auto-1.27.3-*` |
| Existing orgs / repos / users | unchanged (DB upgrade path is forward-compatible within 1.27.x) |

## Risk

Low. 1.27.x → 1.27.3 is a patch-level bump. No migrations required beyond what 1.27.0 → 1.27.3 already covers upstream. Existing tokens, repos, projects, kanban cards, comments, and access controls are unaffected.

## Refs

- Tracking: admin/brencher#63
- Closed upstream feature request: go-gitea/gitea#14299
- Closed upstream agentic-workflows request: go-gitea/gitea#37151
- Projects API merge commit: go-gitea/gitea@7fae3d5db (PR #38691)
- 1.27.3 release notes: go-gitea/gitea/releases/tag/v1.27.3
- CVE-2024-45337: go-gitea/gitea/security/advisories/GHSA-7hqw-9c4g-2v25

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: alex <alex@rudenk.local>
Reviewed-on: #37
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-10-06 18:59:33 +02:00
admin e9de263ee1 pocs (#51)
Reviewed-on: #51
Co-authored-by: rudolf <rudolfss13@gmail.com>
2026-10-05 23:54:20 +02:00
hermesandadmin 82487b1565 [ready-to-test] feat(hermes): use NFS volumes on odroid SSD (#46)
release / build (push) Successful in 2m50s
## Summary

Configure the `hermes` stack persistent volumes as NFS-backed volumes on the SSD of `odroid`.

Changed only:

- `hermes_gateway_data` → `192.168.1.96:/root/volumes/hermes/gateway`
- `hermes_agent_data` → `192.168.1.96:/root/volumes/hermes/agent`

`hermes_squid` is not included.

## Validation

- `docker stack config -c poc/hermes/stack-compose.yml` succeeds.
- `git diff --check` succeeds.
- Diff contains only `poc/hermes/stack-compose.yml`.

## Deployment prerequisite

Before deploy, prepare the NFS export and copy the existing local volumes according to issue #45:

#45

Do not deploy before verifying the copy, NFS access from `rudolf-T`, and the absence of concurrent writes to the old volumes.

## Tracking

Resolves the storage work in admin/ansible#45:
#45
Co-authored-by: hermes <rudolfss13@gmail.com>
Reviewed-on: #46
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-09-24 23:50:41 +02:00
hermes f071c7fb43 fix(hermes_infra/gitea): add dedicated act_runner cache-server (#34)
## Problem

The built-in `act_runner` cache server binds to an interface unreachable from per-job container networks (`container.network: ""` is the default). `ACTIONS_CACHE_URL` ends up pointing at an unreachable IP, and every CI job burns ~9 minutes on:

```
::warning::Failed to restore: getCacheEntry failed: connect ETIMEDOUT 192.168.112.21:37051
::warning::Failed to save:    reserveCache  failed: connect ETIMEDOUT 192.168.112.21:37051
```

Measured on `admin/brencher#15` (https://gitea.rudolf.keenetic.link/admin/brencher/actions/runs/16):

| Job     | wall-clock | of which dead air on cache |
|---------|------------|----------------------------|
| 3.12.3  | 12m 40s    | ~9m (271s × 2 timeouts)    |
| 3.13    | 11m 13s    | ~9m                        |
| 3.14    | 11m 17s    | ~9m                        |

So even though `python-package.yml` enables `cache: 'pip'`, the cache backend is unreachable, jobs hit `pip install` cold every time, and CI ends up ~4x slower than necessary.

## Fix

Run a dedicated `act_runner cache-server` container on the same overlay network as the runner, and point the runner at it via `external_server`. Shared secret comes from a Docker secret mounted into both containers and read via `ACT_RUNNER_EXTERNAL_SECRET_FILE`.

## Changes

- `poc/gitea/stack-compose.yml`:
  - New `cache_server` service (`command: ["cache-server"]`) on the `gitea` overlay with a `cache_data` named volume.
  - `runner` and `cache_server` both mount the external Docker secret `gitea_cache_secret` at `/run/secrets/gitea_cache_secret` and set `ACT_RUNNER_EXTERNAL_SECRET_FILE` accordingly.
  - Top-level `secrets:` block declares `gitea_cache_secret` as `external: true`, with the create command commented inline next to it.
- `poc/gitea/config.yaml`: point `cache.{host,port,external_server}` at `gitea_cache_server:37051`; `external_secret` left empty because the secret is loaded from the file.

## Verification

- Both YAMLs parse (PyYAML).
- Service name `gitea_cache_server` resolves on the `gitea` overlay via Swarm service-name DNS.
- `docker secret inspect gitea_cache_secret` works after the one-time create step.

## Deploy notes

1. On the swarm manager, create the secret once:
   ```
   echo -n "$(openssl rand -hex 32)" | docker secret create gitea_cache_secret -
   ```
2. `docker stack deploy -c stack-compose.yml gitea`.
3. Re-run a CI job and confirm cache `restore`/`save` log lines no longer ETIMEDOUT.

## Related

- Related: admin/brencher#15 — `python-package.yml` enables `cache: 'pip'` and was timing out for the reason this PR fixes.
- Refs: gitea/actions/runs/16 jobs #248/249/250.

## Supersedes

- Supersedes: admin/ansible#33 — first attempt was based on a stale `origin/master` and accidentally included `hermes_squid/` changes from the actual upstream merge. The current branch is rebased on `admin/master` (`c3b7128`) and only touches `poc/gitea/`.Reviewed-on: http://192.168.1.96/admin/ansible/pulls/34
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-09-04 08:11:41 +02:00
admin 72dcdcf12e x 2026-08-23 21:05:36 +02:00
admin 94ff81ae60 x 2026-08-23 20:54:15 +02:00
admin de4de846be x 2026-08-12 22:33:30 +02:00
admin b3915e9428 x 2026-08-12 21:07:27 +02:00
admin 3aaa4b87bf x 2026-08-12 13:05:17 +02:00
admin 8e29e94f59 x 2026-08-12 12:51:45 +02:00
admin a7add7e894 x 2026-08-12 12:44:27 +02:00
admin 78d2c260fd gitea 2026-08-11 21:45:35 +02:00
admin 7112ff4efe x 2026-08-01 23:20:30 +02:00
admin ea12d7e7f9 gitea 2026-07-26 20:46:33 +02:00
admin c6c1e636c8 hermes 2026-06-28 22:41:16 +02:00
7b1d8d8226 Ansible/copilot/update ansible version to 2 7 5 (#5)
* feat: update immich v2.5.6 → v2.7.5

Agent-Logs-Url: https://github.com/rudolf1/uber_backup/sessions/288ed0cf-5c32-4ba8-9df9-6fec2d899afc

Co-authored-by: rudolf1 <5525769+rudolf1@users.noreply.github.com>

* Update Redis digest from immich docker-compose.prod.yml

Agent-Logs-Url: https://github.com/rudolf1/uber_backup/sessions/0fd33671-72d6-47fd-bbf2-a9ccbacdca5a

Co-authored-by: rudolf1 <5525769+rudolf1@users.noreply.github.com>

* Disable healthcheck for server service

Agent-Logs-Url: https://github.com/rudolf1/uber_backup/sessions/dbff4537-9c0c-4d7a-972a-1f73b8fa38c6

Co-authored-by: rudolf1 <5525769+rudolf1@users.noreply.github.com>

* Rollback Immich upload mount path change

Agent-Logs-Url: https://github.com/rudolf1/uber_backup/sessions/1b2c0587-8cc5-4ee6-a592-571ef0aedbd5

Co-authored-by: rudolf1 <5525769+rudolf1@users.noreply.github.com>

* revert: restore immich server healthcheck settings

Agent-Logs-Url: https://github.com/rudolf1/uber_backup/sessions/c43105ab-1893-4c2a-bbdc-7621fe566a61

Co-authored-by: rudolf1 <5525769+rudolf1@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rudolf1 <5525769+rudolf1@users.noreply.github.com>
2026-05-23 12:36:14 +02:00
admin 320c1ba097 Ansible/immich up (#2)
* immich up

* up

* up

* up

* up

* up

* immich up

* up
2026-02-11 21:01:29 +01:00
admin 2327b76171 immich up 2026-02-08 14:17:10 +01:00
admin 96ba30718a immich readme 2025-12-23 12:21:12 +01:00
admin adf6a18dfb Ansible/immich up (#1)
* immich up

* immich 2.4.1
2025-12-20 15:17:36 +01:00
admin 99b148a07e immich up 2025-10-16 19:02:25 +02:00
admin e73c7d6e98 immich 2025-09-23 12:50:43 +02:00
admin 2b734aa078 immich 2025-09-16 22:14:02 +02:00
admin 91458d6b2c immich 2025-09-16 21:37:47 +02:00
admin 8d1651a561 improvements 2025-06-02 23:56:25 +02:00
admin 028a2aaf27 immich expose postgre 2025-05-16 17:56:03 +02:00
admin 565fc10054 immich 2025-05-10 23:51:08 +02:00
admin 7d7d6d7546 immich 2025-05-08 21:43:59 +02:00