Permalink
Browse files

Updated README

  • Loading branch information...
1 parent 3bdf565 commit 0a30c577847dc265f8b1ba7109a1fbae64f7264f @EricR committed Jun 9, 2012
Showing with 20 additions and 2 deletions.
  1. BIN image_sorcery-1.0.1.gem
  2. BIN image_sorcery-1.0.2.gem
  3. +18 −0 image_sorcery.gemspec
  4. +2 −2 readme.markdown
View
BIN image_sorcery-1.0.1.gem
Binary file not shown.
View
BIN image_sorcery-1.0.2.gem
Binary file not shown.
View
18 image_sorcery.gemspec
@@ -0,0 +1,18 @@
+lib = File.expand_path('../lib/', __FILE__)
+$:.unshift lib unless $:.include?(lib)
+
+require 'bundler/version'
+
+Gem::Specification.new do |s|
+ s.name = "image_sorcery"
+ s.version = "1.0.2"
+ s.platform = Gem::Platform::RUBY
+ s.authors = ["Eric Rafaloff"]
+ s.email = ["hello@ericrafaloff.com"]
+ s.homepage = "http://github.com/ericr/image_sorcery"
+ s.summary = "A ruby ImageMagick library that doesn't suck."
+ s.description = "A ruby ImageMagick library that doesn't suck."
+ s.files = Dir.glob("{lib}/**/*") + %w(README.markdown)
+ s.require_path = 'lib'
+ s.add_runtime_dependency "subexec"
+end
View
4 readme.markdown
@@ -2,12 +2,12 @@ Image Sorcery allows you to leverage all three of ImageMagick's command line too
## Why?
-Several other ImageMagick libraries exist for Ruby, but most have at least one of two issues:
+At [Fol.io](http://fol.io), we need server-side image processing to work well and bend to our will. I wrote this because most of the ImageMagick libraries out there for Ruby suffer from at least one of two problems:
* Large memory consumption/leaking
* Doesn't expose the entire ImageMagick library
-Due to the way Image Sorcery was written, it manages to avoid both of these issues.
+Due to the way Image Sorcery was written, it manages to avoid both of these problems.
## Installation

0 comments on commit 0a30c57

Please sign in to comment.