Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Settings API writes mutable values to /app/.env, which is part of the container filesystem and is lost during Docker recreation.
Root cause
The persistent /config mount was not used as the dotenv write/load source, and Bun could continue loading the volatile /app/.env.
Fix
Migrate legacy /app/.env to /config/.env, expose the persistent file through /app/.env for Bun startup loading, write atomically with restrictive permissions, and make the Compose config mount writable.
This complements #104: that PR separates container environment provenance from persisted dotenv values, while this PR makes the persisted dotenv physically durable across container recreation.
Tests