Skip to content

fix(daemon): DATABASE_URL from app.env before the cache (0.4.2) - #77

Merged
sh1pt-actions-fleet[bot] merged 1 commit into
masterfrom
fix/daemon-db-from-app-env
Oct 29, 2026
Merged

sh1pt-actions-fleet[bot] merged 1 commit into
masterfrom
fix/daemon-db-from-app-env

Conversation

@sh1pt-actions-fleet

Copy link
Copy Markdown
Contributor

The Postgres password was rotated in app.env. The directory daemon only tried env, its .database-url cache and the vault (which is stale), so it crash-looped with password authentication failed for user "postgres". Every Deploy to dev2 since #74 failed at the daemon restart step (exit 3, activating).

  • scripts/daemon.mjs: app.env is tried after env and before the cache, and a hit refreshes the cache. secretEnv shares the same appEnv() reader.
  • On prod I already refreshed the cache by hand (backup .database-url.bak-002), and the daemon is active.

🤖 Generated with Claude Code

…cache (0.4.2)

The Postgres password was rotated in app.env, but the daemon only tried env,
its .database-url cache and the stale vault, so it crash-looped with
'password authentication failed' and every deploy since #74 failed at the
daemon restart step. app.env is now tried before the cache and refreshes it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sh1pt-actions-fleet
sh1pt-actions-fleet Bot merged commit 7d9b3ea into master Oct 29, 2026
3 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