dotfiles for secrets and semi-secrets
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7.8k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
Is there a convention for semi-secret things like ~/.ssh/config and ~/.aws/config? These aren't credential but I still don't want to check in IP addresses for private cloud boxes and what not. I made a solution that symlinks out of a ~/.dotfiles-private but wanted to see if there was already a supported path in this project.
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No project files or tests are named. Start by reading the repository's existing dotfile layout and conventions, then compare them with the proposed ~/.dotfiles-private approach and the ~/.ssh/config and ~/.aws/config examples. Done would require an agreed, documented supported path for semi-secret configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100