sander/Hostityourself
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

remove: unnecessary app restart loop from start.sh

Browse source 
Without podman system migrate, compose down/up only touches infra
containers. Deployed hiy-* containers are never stopped during a
platform restart so they need no special handling there.

The restart loop stays in boot.sh where it is needed (system reboot
stops all containers).

https://claude.ai/code/session_01FKCW3FDjNFj6jve4niMFXH
This commit is contained in:
Claude 2026-03-24 12:36:03 +00:00
parent 9fbbdf62ee
commit 31944d128b
No known key found for this signature in database
1 changed files with 0 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
infra/start.sh
View file

@ -182,14 +182,6 @@ make -C "$SCRIPT_DIR" build
podman compose --env-file "$REPO_ROOT/.env" -f "$SCRIPT_DIR/docker-compose.yml" down podman compose --env-file "$REPO_ROOT/.env" -f "$SCRIPT_DIR/docker-compose.yml" down
podman compose --env-file "$REPO_ROOT/.env" -f "$SCRIPT_DIR/docker-compose.yml" up -d podman compose --env-file "$REPO_ROOT/.env" -f "$SCRIPT_DIR/docker-compose.yml" up -d
# ── Restart deployed app containers (stopped by podman system migrate above) ───
podman ps -a --filter "status=exited" --format "{{.Names}}" \
| grep '^hiy-' \
| while IFS= read -r name; do
echo "[hiy] Restarting app: $name"
podman start "$name" || true
done
# ── Install systemd user service for auto-start on boot ─────────────────────── # ── Install systemd user service for auto-start on boot ───────────────────────
# Uses a user-level (rootless) service so Podman's UID namespace is preserved. # Uses a user-level (rootless) service so Podman's UID namespace is preserved.
# loginctl enable-linger lets the service start even without an active login. # loginctl enable-linger lets the service start even without an active login.