Dotfiles and dev tools provisioned by Ansible

http://palcu.blogspot.com/2014/06/dotfiles-and-dev-tools-provisioned-by.html

by palcu • 12 years ago

19 21 12 years ago

palcu.blogspot.com

aw3c2• 12 years 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

palcu3• 12 years 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• 12 years 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:

e.g. 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));})();

shock7• 12 years 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.

buster2• 12 years 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).

shock7• 12 years 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.

buster2• 12 years 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...

palcu3• 12 years ago

I was also using a simple bootstrap script and I too felt I was "killing mosquitos with a bazooka" using Ansible.

But I wanted to symlink my Sublime settings. That meant tinkering with shell code and separating the files in different dirs. Then I wanted to preinstall my Brew apps, but only for Mac.

So these tasks pilled up in shell scripts and became ugly. So Ansible, with it's easy YAML configs, is the perfect tool for a dev like me that wants to setup machines and maintain the configurations synced.

captn3m02• 12 years ago

You should take a look at GNU stow. I also felt the same frustration as my bootstrap script got ugly and uglier. And then I shifted to stow. And now its just a single line:

    stow * --target ~

With respect to ansible, I've been thinking of managing my laptop using just ansible to install new packages, and update configuration (apache, sshd and so on). Kinda like chef-solo, but using ansible. Has anyone done anything like that?

peterhajas• 12 years 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), 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/) 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/) 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).

shock7• 12 years 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.

e12e• 12 years ago

I generally prefer xstow[1] to GNU Stow (if for no other reason than that it doesn't require perl) -- and I couldn't find a reference to --no-folding -- however, at least xstow appear to do the right thing:

    stow $ find ..
    ..
    ../stow
    ../stow/a
    ../stow/a/c
    ../stow/a/c/a
    ../stow/a/c/b
    ../stow/b
    ../stow/b/c
    ../stow/b/c/c
    ../stow/b/c/c/a

    $ xstow b
    $ ls -l ..
    total 4
    lrwxrwxrwx 1 e12e e12e    8 Jun 22 16:47 c -> stow/b/c
    drwxr-xr-x 4 e12e e12e 4096 Jun 22 16:44 stow
   
    #drumrolll...
    $ xstow a
    $ ls -l ..
    total 8
    drwxr-xr-x 2 e12e e12e 4096 Jun 22 16:48 c
    drwxr-xr-x 4 e12e e12e 4096 Jun 22 16:44 stow
    e12e@stripe:~/tmp/stowtest/stow $ ls -l ../c
    total 0
    lrwxrwxrwx 1 e12e e12e 13 Jun 22 16:48 a -> ../stow/a/c/a
    lrwxrwxrwx 1 e12e e12e 13 Jun 22 16:48 b -> ../stow/a/c/b
    lrwxrwxrwx 1 e12e e12e 13 Jun 22 16:48 c -> ../stow/b/c/c

So as long as the symlink is managed by (xstow) -- subdirs will be created as needed. If your point was more about mixing (x)stow'ed and non-stowed files in directories, then you would still want to make sure (x)stow makes the directories, and only symlinks files.

I'm not sure if there's an (easy) way to make xstow do that.

[1] http://xstow.sourceforge.net/

Dotfiles and dev tools provisioned by Ansible

Related Stories