webpro / awesome-dotfiles Goto Github PK

Link: https://news.ycombinator.com/item?id=11071754
From same link

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 on…
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.

Probably this guide should at least mention the XDG Base Dir Spec.

It's sad to see $HOME's cluttered with dotfiles, while everything related to configuration can, and most likely should be placed into $XDG_CONFIG_HOME.

Arch wiki has a very good overview of general XDG base dir support at https://wiki.archlinux.org/index.php/XDG_Base_Directory_support, so this can be a good pointer on how to organize your own dotfiles.

https://github.com/yunielrc/ydf

I developed this tool

Hey @webpro

I made this - https://github.com/Addvilz/dots - do you think it could be useful to add this to the list? I think it's a good example on how to automate both installation and maintenance of a dev / mixed purpose workstation.

I would like to suggest this tool for people triying to clean their home directory from dotfiles and other unwanted directories manually:

xdg-ninja

It's a tool which analyze your $HOME and generate a user currated list of advices and solutions to clean the mess.

Really helpful when you don't know where to start.

Hey @webpro

I made this - https://github.com/tenhishadow/dotfiles
I think it could be useful here as an example with a bit different way of installing it( even from existing ansible-managed dots )

Pull requests are not been aproved by Travis.

#17.1 failed

Issues :-(

Links

1. [L017] 301 http://code.tutsplus.com/tutorials/setting-up-a-mac-dev-machine-from-zero-to-hero-with-dotfiles-part-2--cms-23145 → https://code.tutsplus.com/tutorials/setting-up-a-mac-dev-machine-from-zero-to-hero-with-dotfiles-part-2--cms-23145
2. [L017] 301 http://code.tutsplus.com/tutorials/setting-up-a-mac-dev-machine-from-zero-to-hero-with-dotfiles--net-35449 → https://code.tutsplus.com/tutorials/setting-up-a-mac-dev-machine-from-zero-to-hero-with-dotfiles--net-35449
3. [L088] 301 http://freshshell.com/ → https://freshshell.com/
4. [L108] 301 https://github.com/kevinSuttle/OSXDefaults → https://github.com/kevinSuttle/macOS-Defaults

I tested the links, but they are actually working. :s

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

It is currently being used by

• https://github.com/vsouza/awesome-ios
• https://github.com/matteocrippa/awesome-swift
• https://github.com/dkhamsing/open-source-ios-apps

Examples

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄

This repo misses a license. You could use https://github.com/sindresorhus/awesome#license as inspiration.