Skip to content

ops: chown .deploy-state to the deploy user #297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralyodio merged 1 commit into from
Sep 24, 2026
Merged

ops: chown .deploy-state to the deploy user #297

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion ops/selfhost/server/setup-app-host.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,11 @@ log() { printf '\n===> %s\n' "$*"; }

log "App files to $USER_NAME, supabase/ to root"
install -d -o "$USER_NAME" -g "$USER_NAME" -m 2750 "$ROOT"
for f in app.env deploy.env docker-compose.app.yml deploy-app.sh; do
# .deploy-state is included deliberately: running deploy-app.sh once as root
# (which is the natural thing to do during the initial migration) leaves a
# root-owned state file, and every later CI deploy then succeeds all the way
# through the health check and fails on the very last line writing it.
for f in app.env deploy.env docker-compose.app.yml deploy-app.sh .deploy-state; do
[ -e "$ROOT/$f" ] && chown "$USER_NAME:$USER_NAME" "$ROOT/$f"
done
[ -e "$ROOT/app.env" ] && chmod 600 "$ROOT/app.env"
Expand Down