moves sensitive keys to gitignored folder #747
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
Osprey
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
resilience
Tom's Wishlist
type: bug
type: discussion
type: error handling
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/spee.ch#747
Loading…
Reference in a new issue
No description provided.
Delete branch "sensitiveKeys"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Old behavior: siteConfig had some sensitive passwords.
New behavior: passwords are stored in ./config which is gitignored.
Looks good
When we spoke, I may have said
/config
, which I meant/site/config
in context.We don't need a separate directory, but if we use one I would suggest using
site/secrets
.Ok. What you said was literally true: The spee.ch repo's gitignore did indeed cover /config even though the folder didn't exist. Where would you like the gitignore for the site repo?
Will need to update environments before merging/deploying