Daniel Maksymilian Syrnicki
61c7ee232c
End-to-end VM test today (2026-04-15) validated the resource manager golden path but exposed four things blocking "dein-Vater-tauglich": no way to configure an app without SSH+editor, no openssh, no nano, keyboard stuck on US, and a samba healthcheck that cried wolf. Resource-manager side: - Manifest schema gains optional `settings` list (name/label/ description/type/required/default) and `description_long`. - Bundled-app install opens a form rendered from the manifest; submit carries values to `POST /api/apps/install` which writes them into the new app's `.env` before the placeholder check runs. - Installed apps grow an "Einstellungen" button that merges a partial settings dict into the existing `.env` (unsubmitted password fields = keep current), then reconciles to restart. - New endpoints: `GET/POST /api/apps/<name>/settings`. Passwords are never returned to the client. - Fileshare manifest declares its SMB_USER/SMB_PASSWORD settings in German with help text. ISO side (so the next build is actually usable on the TTY): - Add `openssh` to the package list + `sshd` to enabled services. `archinstall: true` in 4.x did not install openssh-server. - Add `nano` — `vim` was the only editor pitched at users, which is brutal for first-timers (and was missing anyway). - Keyboard layout follows the installer language (`de→de`, `pl→pl`, `en→us`) instead of hardcoded `us`. A German user couldn't type `/` or `-` at the console, making even `sudo nano` painful. - Disable the dperson/samba healthcheck in the compose override — it timed out on every probe while the share itself worked fine. 19 new tests (manifest parsing + settings-merge + two new API endpoints over live HTTP); 94 total, format + lint clean. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
39 lines
1.4 KiB
YAML
39 lines
1.4 KiB
YAML
# Furtka fileshare — SMB share via dperson/samba.
|
|
#
|
|
# The volume `furtka_fileshare_files` is created by the Furtka reconciler
|
|
# from the manifest's "volumes" list before this compose file is brought up;
|
|
# it's referenced as `external: true` here so docker compose doesn't try
|
|
# to manage its lifecycle.
|
|
#
|
|
# TODO(image-pin): `:latest` is shaky for production — pin to a digest
|
|
# (`dperson/samba@sha256:...`) or a stable tag once we've verified one
|
|
# against the upstream registry. For the MVP run we accept the drift
|
|
# risk to keep the install reproducible against whatever the upstream
|
|
# image happens to be on test day; revisit before any non-developer
|
|
# touches this.
|
|
|
|
services:
|
|
smbd:
|
|
image: dperson/samba:latest
|
|
restart: unless-stopped
|
|
network_mode: host
|
|
# The upstream image's HEALTHCHECK times out under normal operation on
|
|
# our setup (2026-04-15 VM test — all 6 probes failed while the share
|
|
# was reachable from clients). Disable to avoid a permanently-"unhealthy"
|
|
# container that scares users reading `docker ps`.
|
|
healthcheck:
|
|
disable: true
|
|
environment:
|
|
- USERID=1000
|
|
- GROUPID=1000
|
|
- TZ=Europe/Berlin
|
|
command: >
|
|
-u "${SMB_USER};${SMB_PASSWORD}"
|
|
-s "files;/mount;yes;no;no;${SMB_USER}"
|
|
-p
|
|
volumes:
|
|
- furtka_fileshare_files:/mount
|
|
|
|
volumes:
|
|
furtka_fileshare_files:
|
|
external: true
|