https://github.com/yardnsm/.config

:zap: Welcome to my world. Managed by https://github.com/yardnsm/.setup
https://github.com/yardnsm/.config

bash dotfiles git macos shell tmux vim zsh

Last synced: about 2 months ago
JSON representation

:zap: Welcome to my world. Managed by https://github.com/yardnsm/.setup

• Host: GitHub
• URL: https://github.com/yardnsm/.config
• Owner: yardnsm
• License: mit
• Created: 2016-02-21T18:42:12.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2024-08-03T20:54:14.000Z (about 2 months ago)
• Last Synced: 2024-08-04T16:53:03.858Z (about 2 months ago)
• Topics: bash, dotfiles, git, macos, shell, tmux, vim, zsh
• Language: Shell
• Homepage:
• Size: 6.81 MB
• Stars: 39
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# .config

These are my dotfiles. A collection of zsh, git, vim and macOS configurations. I built this

repository completely from scratch, with the main focus of organization in mind.

This repository used to have **a lot** of installation and setup-related scripts, but I realized

this method of organization was probably a bit overkill and not so portable between machines. So,

currently, this repository contains my entire `~/.config` directory (well, not exactly the *entire*

directory, but most of it).

## Installation

The setup scripts moved to a new repository, located at

[yardnsm/.setup](https://github.com/yardnsm/.setup).

## Protecting Secrets

I'm using `.gitattributes` filters to mask out sensitive data (this is taken from

[rafi/.config](https://github.com/rafi/.config)).

After cloning this repository, you should setup the custom filters (the installer already does this

automatically):

```bash

git config --local filter.vault.clean "sed -f ~/.config/clean.sed"

git config --local filter.vault.smudge "sed -f ~/.config/smudge.sed"

```

And create the `smudge.sed`, then fill it up. The installer already does this, but you can also

convert the `clean.sed` file to a valid template:

```bash

sed 's/^.*\({{.*}}\).*$/s\/\1\/value\//' clean.sed > smudge.sed

```

Now, whenever you stage files, the `clean.sed` will prevent secrets being committed. And on

checkout, the `smudge.sed` will inject your secrets into their proper placeholders. **The

`smudge.sed` file is ignored from being committed.**

----------------------------------------------------------------------------------------------------

## License

MIT © [Yarden Sod-Moriah](http://yardnsm.net/)