Gemoji 1.3.1

added 🖕

LICENSE

@@ -1,14 +1,14 @@
 octocat, squirrel, shipit
-Copyright (c) 2012 GitHub Inc. All rights reserved.
+Copyright (c) 2013 GitHub Inc. All rights reserved.
 
-bowtie, neckbeard
-Copyright (c) 2012 37signals, LLC. All rights reserved.
+bowtie, neckbeard, fu
+Copyright (c) 2013 37signals, LLC. All rights reserved.
 
 feelsgood, finnadie, goberserk, godmode, hurtrealbad, rage 1-4, suspect
-Copyright (c) 2012 id Software. All rights reserved.
+Copyright (c) 2013 id Software. All rights reserved.
 
 trollface
-Copyright (c) 2012 whynne@deviantart. All rights reserved.
+Copyright (c) 2013 whynne@deviantart. All rights reserved.
 
 All other images
-Copyright (c) 2012 Apple Inc. All rights reserved.
+Copyright (c) 2013 Apple Inc. All rights reserved.

README.md

@@ -17,6 +17,15 @@ gem 'gemoji'
 
 Images can be copied to your public directory with `rake emoji` in your Rails app. This is the recommended approach since the images will be available at a consistent location. This works best with cached formatted user content generated by tools like [html-pipeline](https://github.com/jch/html-pipeline).
 
+``` ruby
+# Rakefile
+load 'tasks/emoji.rake'
+```
+
+```
+$ rake emoji
+```
+
 **Assets Precompiling**
 
 If you must, you can manually add all the images to your asset load path.
@@ -33,7 +42,7 @@ Then have them compiled to public on deploy.
 config.assets.precompile << "emoji/*.png"
 ```
 
-**WARNING** Since there are a ton of images, just adding the path may slow down other lookups if you aren't using it. Compiling all the emojis on deploy will add overhead to your deploy if even the images haven't changed. Theres just so many more superfluous files to iterate over. Also, the urls will be fingerprinted which many not be ideal for referencing from cached content.
+**WARNING** Since there are a ton of images, just adding the path may slow down other lookups if you aren't using it. Compiling all the emojis on deploy will add overhead to your deploy if even the images haven't changed. Theres just so many more superfluous files to iterate over. Also, the urls will be fingerprinted which may not be ideal for referencing from cached content.
 
 
 Example Rails Helper

gemoji.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name    = "gemoji"
-  s.version = "1.3.0"
+  s.version = "1.3.1"
   s.summary = "Emoji Assets"
   s.description = "Emoji assets"
 

lib/tasks/emoji.rake

@@ -1,3 +1,4 @@
+desc "Copy emoji to the Rails `public/images/emoji` directory"
 task :emoji => :environment do
   require 'emoji'