StreakyCobra

10 年前議論

Really nice, well explained. I'll know where to point people to when I need to present this techique. Thanks!

10 年前議論

Nice thanks. I don't have twitter. Also don't present me as the inventor of this technique because I'm not. I've read this long time ago on some dark corners of the internet :-) I'm just pointing it out.

StreakyCobra

10 年前議論

It's probably better if you do it then :-) I would probably skip some important parts trying to explain because I'm too much used to it already.

StreakyCobra

10 年前議論

There are probably already posts about this: I didn't invented it, I read it somewhere… but it was long time ago, I don't remember where.

StreakyCobra

10 年前議論

It's because we specify to git that the working tree is the home folder. For it the versionning doesn't happen in ".myconf", but directly in the home folder

StreakyCobra

10 年前議論

Because the working tree is already your home folder, you don't need to also have a copy of these files in ".myconf/".

StreakyCobra

10 年前議論

I have a "master" branch, and some "computer" branches. When changes are required for all computer, I do it in "master", and then update each branch by doing a "git merge master".

StreakyCobra

10 年前議論

I use:

    git init --bare $HOME/.myconf
    alias config='/usr/bin/git --git-dir=$HOME/.myconf/ --work-tree=$HOME'
    config config status.showUntrackedFiles no

where my ~/.myconf directory is a git bare repository. Then any file within the home folder can be versioned with normal commands like:

    config status
    config add .vimrc
    config commit -m "Add vimrc"
    config add .config/redshift.conf
    config commit -m "Add redshift config"
    config push

And so one…

No extra tooling, no symlinks, files are tracked on a version control system, you can use different branches for different computers, you can replicate you configuration easily on new installation.

StreakyCobra

投稿

Secure AWS Access Keys on Your Laptop

コメント