docs: clarify safe local env setup#133
Open
b1rdmania wants to merge 1 commit into
Open
Conversation
amal66
added a commit
to amal66/mike
that referenced
this pull request
May 25, 2026
Chapter: 33 - Safe local development. Plain-English map: Document how to avoid using production databases, production buckets, real client documents, or browser-exposed service-role keys during local testing. Why it matters: New contributors can accidentally leak sensitive data or admin credentials while only trying to run the app. The docs should prevent that mistake early. Principle: Good setup docs are a security control. Precedent borrowed: Upstream PR willchen96#133. Upstream base: willchen96/mike@d39f580. Original local commit: 5e3608b.
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.
Summary
Validation
Documentation-only change.