Skip to content

Upload each deploy into its own private directory on the host - #407

Merged
demegire merged 1 commit into
mainfrom
fix/deploy-upload-dir
Oct 13, 2026
Merged

demegire merged 1 commit into
mainfrom
fix/deploy-upload-dir

Conversation

@demegire

Copy link
Copy Markdown
Contributor

deploy.sh uploaded to fixed names in /tmp. When a different account deployed next (a teammate, or the new deploy-staging workflow's service account), the earlier files were still owned by their uploader and scp was refused. This is the failure in the first deploy-staging runs after #406.

Each deploy now creates its own mktemp -d /tmp/tin-deploy.XXXXXXXXXX on the host, uploads there, passes it to activate_release.sh as TIN_LITE_UPLOAD_DIR (validated; /tmp still works for the old layout), and removes it afterwards whether or not the deploy succeeded.

Verified: deployed this branch to staging with TIN_LITE_DEPLOY_TARGET=staging infra/deploy.sh. Exit 0, both health checks passed, no upload directory left behind. The deploy-staging workflow is dispatched on this branch as a second check.

🤖 Generated with Claude Code

Fixed names in /tmp collide when a different account (a teammate, or the
staging deploy workflow) deploys after you: the earlier files stay owned by
their uploader and the next scp is refused.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@demegire
demegire requested a review from a team as a code owner October 13, 2026 12:41
@demegire
demegire merged commit 1514d94 into main Oct 13, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant