$ git push origin master
...
warning: updating the current branch
warning: Updating the currently checked out branch may cause confusion,
warning: as the index and work tree do not reflect changes that are in HEAD.
warning: As a result, you may see the changes you just pushed into it
warning: reverted when you run 'git diff' over there, and you may want
warning: to run 'git reset --hard' before starting to work to recover.
warning:
warning: You can set 'receive.denyCurrentBranch' configuration variable to
warning: 'refuse' in the remote repository to forbid pushing into its
warning: current branch.
warning: To allow pushing into the current branch, you can set it to 'ignore';
warning: but this is not recommended unless you arranged to update its work
warning: tree to match what you pushed in some other way.
warning:
warning: To squelch this message, you can set it to 'warn'.
warning:
warning: Note that the default will change in a future version of git
warning: to refuse updating the current branch unless you have the
warning: configuration variable set to either 'ignore' or 'warn'.

Woah! After some research, this is because I didn’t set up my remote folder as “bare”. A non-bare repository has a working copy attached to it, and this warning is telling you that said working copy exists and is currently checked out to the branch you’re trying to push to.

This is bad, because if you were pushing to a co-worker’s machine, then when they go to commit or run a diff, things will go awry. In this case, I just didn’t set up the repository correctly (it was the first one I’d done!) so I wasn’t in danger of losing anything.

The fix is to use --bare:
git init --bare or git clone --bare

~$ bundle install
...
Installing do_sqlite3 (0.10.0) from rubygems repository at
  http://gemcutter.org/ with native extensions
  /usr/local/lib/site_ruby/1.8/rubygems/installer.rb:482:in
  `build_extensions':
ERROR: Failed to build gem native extension.
  (Gem::Installer::ExtensionBuildError)

/usr/bin/ruby1.8 extconf.rb
checking for sqlite3.h... no
*** extconf.rb failed ***
...

The key is the line: checking for sqlite3.h... no
The do_sqlite3 gem gets compiled natively, but the development headers weren’t installed on the system and so the compilation won’t work.

Install them:

~$ sudo apt-get install sqlite3
~$ sudo apt-get install libsqlite3-dev

Then, re-bundle:

~$ bundle install

• Change your background back to an image.
• Turn off the Desktop Window Manager. (Note: this will turn off mouse arrow effects)

Load your formats into Time::DATE_FORMATS

Time::DATE_FORMATS[:ymd] = "%Y-%m-%d"

Use like so:

@christmas_post.created_at.to_s(:ymd)
# => "2009-12-25"

The Kansas City skyline at night.  Very nice picture.

Kansas City’s Nelson-Atkins art museum has an installation of four giant shuttlecocks on the lawn.  A great place to take friends for a picture when you’re bored.

Progressive enhancement is a strategy for web design that emphasizes accessibility, semantic markup, and external stylesheet and scripting technologies. Progressive enhancement uses web technologies in a layered fashion that allows everyone to access the basic content and functionality of a web page, using any browser or Internet connection, while also providing those with better bandwidth or more advanced browser software an enhanced version of the page.

http://en.wikipedia.org/wiki/Progressive_enhancement

Kansas City Ruby Users Group | February 2010 | Kyle J. Ginavan | Progressive Enhancement | kcrug.org from Wes Garrison on Vimeo.

Resources:

Nicole Sullivan on Object Oriented CSS

• Slides: http://www.slideshare.net/stubbornella/object-oriented-css
• Code: http://wiki.github.com/stubbornella/oocss/

Other articles:

• A List Apart: Understanding Progressive Enhancement
• Wikipedia: Progressive Enhancement

Kansas City Ruby Users Group | February 2010 | Kyle J. Ginavan | Progressive Enhancement | kcrug.org from Wes Garrison on Vimeo.

Specifically:

mkfifo /var/spool/postfix/public/pickup
ps aux | grep mail
kill
sudo /etc/init.d/postfix restart


fatal: unable to create '.git/index.lock': File exists

The fix:
Got to your project’s shared/cached-copy/.git folder and delete index.lock . It shouldn’t ever get hung up like that, but it happened to me.

An original application completed for Rails Rumble 2009.

Lowdown helps keep your development project on track by helping developers, designers, project managers and owners all focus on satisfying stakeholders.

Built along with Sean Cribbs + Scotty Moon + Paul du Coudray

While leading the competition after judges’ voting ended, we slipped to 4th place after public voting and ended up taking the “Best Appearance” category, which is fantastic.