v0.257.0: the app catalog can speak English (R-560, slice 5 Part A)

The READ PATH for a second language in `.felhom.yml`. An `i18n: {en: …}` sibling block inside the same file; `Metadata.For(lang)` merges it FIELD BY FIELD over the Hungarian, so a missing or blank English field shows the Hungarian one and a half-translated app is a legal, shippable state. `For("hu")` is the parsed struct with `I18n` cleared and nothing else — measured against all 53 real catalog files, copied into `internal/stacks/testdata/catalog/`. Lists replace whole; every other list is matched by its own key, never by position. `For` never writes through the receiver: the metadata is the stack manager's, shared by concurrent requests, and an in-place merge would leak one household's language into another household's page. Pages reach catalog copy only through `LocalizeStacks`/`LocalizeStackPtr`/`MetaFor`, and `TestNoDirectMetaCopyReadOnPages` keeps a named, reasoned allow-list of every direct `.Meta.<copy>` read in `internal/web` so the NEXT page to read one fails the suite instead of quietly rendering Hungarian to an English household. Eight red-proofs. Two of them convicted a hollow TEST rather than the code: a struct copy shares its slices' backing arrays, so the obvious DeepEqual mutation check passed a deliberately broken merge; and a one-entry fixture cannot tell key matching from position matching. Both rewritten, both then seen to fail. MinAgent: 0.131.0 (unchanged). Older controllers are unaffected — `LoadMetadata` uses non-strict `yaml.Unmarshal`, so a pre-0.257.0 box drops the whole block. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-20 14:31:52 +02:00
parent e81ad613ae
commit 60f0a86bd4
60 changed files with 5318 additions and 6 deletions
@@ -0,0 +1,81 @@
+# =============================================================================
+# .felhom.yml - App metadata for felhom-controller
+# =============================================================================
+
+# --- Display info (shown on dashboard) ---
+display_name: "Gitea"
+description: "Könnyű, saját Git szerver webes felülettel"
+category: "dev"
+subdomain: "git"
+slug: "gitea"
+# catalog_since: the date THIS repo last changed this app's pinned images. Any commit that
+# changes an image: line must set this to the same day (see CLAUDE.md).
+catalog_since: "2026-07-18"
+
+# --- Resource hints (displayed on deploy screen) ---
+resources:
+  mem_request: "100M"
+  mem_limit: "512M"
+  pi_compatible: true
+  needs_hdd: false
+
+# --- Deploy fields (first deployment only) ---
+deploy_fields:
+  - env_var: DOMAIN
+    label: "Domain"
+    type: domain
+    description: "A szerver domain neve"
+    locked_after_deploy: true
+
+  - env_var: SUBDOMAIN
+    label: "Aldomain"
+    type: subdomain
+    default: "git"
+    required: true
+    locked_after_deploy: true
+    description: "Az alkalmazás aldomainje"
+
+# --- App info (info page content) ---
+app_info:
+  tagline: "Saját Git szerver - GitHub-szerű felület, privát repók"
+  docs_url: "https://docs.gitea.com/"
+
+  use_cases:
+    - 'Privát Git repozitóriók a saját szerveren'
+    - 'GitHub-szerű felület: pull request, issue, wiki'
+    - 'CI/CD pipeline-ok (Gitea Actions - GitHub Actions kompatibilis)'
+    - 'Szervezetek és csapatok kezelése'
+    - 'Container registry és csomagkezelő'
+
+  first_steps:
+    - 'Nyisd meg a git.DOMAIN címet a böngészőben'
+    - 'Kövesd az első beállítás varázslót'
+    - 'Hozd létre az admin fiókot'
+    - 'Hozd létre az első repozitóriót'
+    - 'Klónozd a repót: git clone https://git.DOMAIN/user/repo.git'
+
+
+# --- Controller-side health probe ---
+healthcheck:
+  checks:
+    - type: api
+      port: 3000
+      # /api/healthz is always available (200) once serving; /api/v1/version 404s pre-install-lock.
+      path: "/api/healthz"
+      expect:
+        status: 200
+
+# --- App-email mapping (apps → in-controller shim → hub → Resend) ---
+# Gitea uses STARTTLS to the shim and trusts its self-signed cert via FORCE_TRUST_SERVER_CERT.
+# Gitea applies GITEA__* env on every boot, so toggling app-email + redeploy takes effect. The From
+# is Gitea's single GITEA__mailer__FROM; USER/PASSWD stay unset (the shim accepts no-auth).
+smtp_mapping:
+  host_var: GITEA__mailer__SMTP_ADDR
+  port_var: GITEA__mailer__SMTP_PORT
+  security_var: GITEA__mailer__PROTOCOL
+  security_value: "smtp+starttls"
+  from_var: GITEA__mailer__FROM
+  from_local: gitea
+  extra:
+    GITEA__mailer__ENABLED: "true"
+    GITEA__mailer__FORCE_TRUST_SERVER_CERT: "true"