5 ms·

Dotfiles and dev tools provisioned by Ansible

19 points by palcu 12y ago

aw3c2 12y ago
That has to be the worst webdesign I have seen this week. Not only does it require JS to show anything but a blank page but it displays an "inner-window" window. Dear web gods, why? http://i.imgur.com/qBHLCac.png http://i.imgur.com/qBHLCac.png
- palcu 12y ago
  I still use Blogspot because moving my posts to another platform would mean too much time lost. I prefer to invest this time in hacking and writing articles. But yes, the desktop experience is a little awful. However, it's the only theme that works flawless on tablets and mobile devices.
- ivank 12y ago
  FWIW, Google Cache can serve you HTML for these Dynamic Views blogs; just prefix the URL with https://webcache.googleusercontent.com/search?q=cache https://webcache.googleusercontent.com/search?q=cache: e.g. https://webcache.googleusercontent.com/search?q=cache:http://palcu.blogspot.com/2014/06/dotfiles-and-dev-tools-provisioned-by.html https://webcache.googleusercontent.com/search?q=cache:http:/... Incidentally, it's the only place you can get HTML for these blogs, and I suspect that Blogspot has special-cased Googlebot to give it HTML instead a pile of JavaScript. For convenience, I have this bookmarklet bound to my 'c' keyword in Firefox: javascript:(function(){window.open('https://webcache.googleusercontent.com/search?q=cache:'+(''+window.location));})();
  - shock 12y ago
    Thanks for the tip. I'm using NoScript/HTTPSwitchboard and have long been frustrated by javascript being required to show even simple posts on blogspot.
buster 12y ago
Why ansible? I'm storing my dotfiles in a private git repo and sync across multiple laptops. Works fine so far. Put the dotfiles and directories into git. Symlink from ~/.vim to ~/dotfiles/.vim and be done with it. (~/dotfiles would contain the git checkout of course).
- shock 12y ago
  I think that's the better way to to it (at least compared to ansible/chef/puppet/etc). I additionally use GNU Stow for doing the symlinking.
  - buster 12y ago
    Sounds interesting. Could you explain a bit more how this works, briefly? I find the GNU stow page not really good to understand and lack some example of how it would be used...
    - captn3m0 12y ago
      I recently shifted to stow as well. You can see my configuration on github[0]. [0]: http://github.com/captn3m0/dotfiles http://github.com/captn3m0/dotfiles
    - shock 12y ago
      Sure, I use a pretty simple setup: I have a ~/dotfiles directory in which I have one directory for each program/entity I want to manage using stow. Let's say I want to manage my GNOME keyrings and my settings for the program EasyStroke. My ~/dotfiles directory would look like this: ~/dotfiles ├── easystroke │ └── .easystroke │ ├── actions-0.5.6 │ └── preferences-0.5.5 └── keyrings └── .local └── share └── keyrings ├── login.keyring └── user.keystore Then, in ~/dotfiles I can do "stow easystroke" and it will create ~/.easystroke and there it will symlink "actions-0.5.6" to ~/dotfiles/easystroke/.easystroke/ actions-0.5.6 and "preferences-0.5.5" to ~/dotfiles/easystroke/.easystroke/preferences-0.5.5
peterhajas 12y ago
Several months ago, I became pretty interested in the idea of a unified computer setup. Between my home computers and work computers, it began weighing on me mentally to have to switch contexts all the time. I'd forget which machine had `wget`, which `fish` functions were installed on which host, etc. The most tedious thing was the process of setting up a new computer: painstakingly finding each and every little configuration I had on my other machines, and copying them over. I'd spend half a day just setting up a new machine. I wanted something better. I first tried Ira's [mackup](https://github.com/lra/mackup https://github.com/lra/mackup), which syncs files to Dropbox. Its catch-all approach scared me, though, as it backs up `fish` history by default. I decided to move to something different. I ended up basing my dotfiles setup on the GNU [stow](https://www.gnu.org/software/stow/ https://www.gnu.org/software/stow/) utility. Here's how it works: - In `~`, I have a git-managed directory `dotfiles` - For every new app I use, I make a new directory in `dotfiles`. For example, `vim`, `fish`, etc. - I run `stow` on all these directories, and it symlinks everything into place I ended up rolling my own update script, but it's pretty trivial. I also made heavy use of Homebrew brewfiles, which can be used to define what commands you would like to run through Homebrew. I also use [Homebrew Cask](http://caskroom.io/ http://caskroom.io/) to install apps. In the end, I now have the exact same configuration on all my machines. For work, I have a separate branch, which has other fish functions / utilities. I recently got a new computer, and I ran the `update.sh` script while I went to lunch. When I came back, my machine was ready to go. Take a look at my setup [here](https://github.com/peterhajas/dotfiles https://github.com/peterhajas/dotfiles).
- shock 12y ago
  I think it would be better to use the "--no-folding" argument to stow in your update.sh script, otherwise stow will do something which I find undesired: - let's say you have a file ~/dotfiles/vim-powerlinefonts/.config/fontconfig/conf.d/10-powerlinefonts.conf and you don't have the ~/.config/fontconfig directory - when you do "stow vim-powerlinefonts" in the dotfiles directory it will create ~/.config/fontconfig as a symlink to your ~/dotfiles/vim-powerlinefonts/.config/fontconfig directory so now you can't add other fontconfig files in ~/.config/fontconfig/conf.d - if instead you do "stow --no-folding vim-powerlinefonts" in the dotfiles directory it will create ~/.config/fontconfig/conf.d/ and there it will symlink 10-powerlinefonts.conf to ~/dotfiles/vim-powerlinefonts/.config/fontconfig/conf.d/10-powerlinefonts.conf, which is usually what you want.

19 points by palcu 12y ago

aw3c2 12y ago

That has to be the worst webdesign I have seen this week. Not only does it require JS to show anything but a blank page but it displays an "inner-window" window. Dear web gods, why? http://i.imgur.com/qBHLCac.png http://i.imgur.com/qBHLCac.png

palcu 12y ago
I still use Blogspot because moving my posts to another platform would mean too much time lost. I prefer to invest this time in hacking and writing articles. But yes, the desktop experience is a little awful. However, it's the only theme that works flawless on tablets and mobile devices.
ivank 12y ago
FWIW, Google Cache can serve you HTML for these Dynamic Views blogs; just prefix the URL with https://webcache.googleusercontent.com/search?q=cache https://webcache.googleusercontent.com/search?q=cache: e.g. https://webcache.googleusercontent.com/search?q=cache:http://palcu.blogspot.com/2014/06/dotfiles-and-dev-tools-provisioned-by.html https://webcache.googleusercontent.com/search?q=cache:http:/... Incidentally, it's the only place you can get HTML for these blogs, and I suspect that Blogspot has special-cased Googlebot to give it HTML instead a pile of JavaScript. For convenience, I have this bookmarklet bound to my 'c' keyword in Firefox: javascript:(function(){window.open('https://webcache.googleusercontent.com/search?q=cache:'+(''+window.location));})();
- shock 12y ago
  Thanks for the tip. I'm using NoScript/HTTPSwitchboard and have long been frustrated by javascript being required to show even simple posts on blogspot.

buster 12y ago

Why ansible? I'm storing my dotfiles in a private git repo and sync across multiple laptops. Works fine so far. Put the dotfiles and directories into git. Symlink from ~/.vim to ~/dotfiles/.vim and be done with it. (~/dotfiles would contain the git checkout of course).

shock 12y ago
I think that's the better way to to it (at least compared to ansible/chef/puppet/etc). I additionally use GNU Stow for doing the symlinking.
- buster 12y ago
  Sounds interesting. Could you explain a bit more how this works, briefly? I find the GNU stow page not really good to understand and lack some example of how it would be used...
  - captn3m0 12y ago
    I recently shifted to stow as well. You can see my configuration on github[0]. [0]: http://github.com/captn3m0/dotfiles http://github.com/captn3m0/dotfiles
  - shock 12y ago
    Sure, I use a pretty simple setup: I have a ~/dotfiles directory in which I have one directory for each program/entity I want to manage using stow. Let's say I want to manage my GNOME keyrings and my settings for the program EasyStroke. My ~/dotfiles directory would look like this: ~/dotfiles ├── easystroke │ └── .easystroke │ ├── actions-0.5.6 │ └── preferences-0.5.5 └── keyrings └── .local └── share └── keyrings ├── login.keyring └── user.keystore Then, in ~/dotfiles I can do "stow easystroke" and it will create ~/.easystroke and there it will symlink "actions-0.5.6" to ~/dotfiles/easystroke/.easystroke/ actions-0.5.6 and "preferences-0.5.5" to ~/dotfiles/easystroke/.easystroke/preferences-0.5.5

peterhajas 12y ago

Several months ago, I became pretty interested in the idea of a unified computer setup. Between my home computers and work computers, it began weighing on me mentally to have to switch contexts all the time. I'd forget which machine had `wget`, which `fish` functions were installed on which host, etc. The most tedious thing was the process of setting up a new computer: painstakingly finding each and every little configuration I had on my other machines, and copying them over. I'd spend half a day just setting up a new machine. I wanted something better. I first tried Ira's [mackup](https://github.com/lra/mackup https://github.com/lra/mackup), which syncs files to Dropbox. Its catch-all approach scared me, though, as it backs up `fish` history by default. I decided to move to something different. I ended up basing my dotfiles setup on the GNU [stow](https://www.gnu.org/software/stow/ https://www.gnu.org/software/stow/) utility. Here's how it works: - In `~`, I have a git-managed directory `dotfiles` - For every new app I use, I make a new directory in `dotfiles`. For example, `vim`, `fish`, etc. - I run `stow` on all these directories, and it symlinks everything into place I ended up rolling my own update script, but it's pretty trivial. I also made heavy use of Homebrew brewfiles, which can be used to define what commands you would like to run through Homebrew. I also use [Homebrew Cask](http://caskroom.io/ http://caskroom.io/) to install apps. In the end, I now have the exact same configuration on all my machines. For work, I have a separate branch, which has other fish functions / utilities. I recently got a new computer, and I ran the `update.sh` script while I went to lunch. When I came back, my machine was ready to go. Take a look at my setup [here](https://github.com/peterhajas/dotfiles https://github.com/peterhajas/dotfiles).

shock 12y ago
I think it would be better to use the "--no-folding" argument to stow in your update.sh script, otherwise stow will do something which I find undesired: - let's say you have a file ~/dotfiles/vim-powerlinefonts/.config/fontconfig/conf.d/10-powerlinefonts.conf and you don't have the ~/.config/fontconfig directory - when you do "stow vim-powerlinefonts" in the dotfiles directory it will create ~/.config/fontconfig as a symlink to your ~/dotfiles/vim-powerlinefonts/.config/fontconfig directory so now you can't add other fontconfig files in ~/.config/fontconfig/conf.d - if instead you do "stow --no-folding vim-powerlinefonts" in the dotfiles directory it will create ~/.config/fontconfig/conf.d/ and there it will symlink 10-powerlinefonts.conf to ~/dotfiles/vim-powerlinefonts/.config/fontconfig/conf.d/10-powerlinefonts.conf, which is usually what you want.