enigmamachine 0.3.1 → 0.3.2

data/README.rdoc

@@ -1,10 +1,11 @@
 = enigmamachine
 
-Enigmamachine is a video processor which queues and encodes videos according
-to target profiles that you define.  Videos must be on a locally mounted
-filesystem.  The processor takes the path to the video, and executes
-one or more ffmpeg commands on the video.  There is a handy web interface for
-defining encoding tasks, and a restful web service which takes encoding commands.
+Enigmamachine is a RESTful web-based video processor which queues and encodes
+videos according to target profiles that you define.  Videos must be on a
+locally mounted filesystem.  The processor takes the path to the video, and
+executes one or more ffmpeg commands on the video.  There is a handy web
+interface for defining encoding tasks, and a restful web service which takes
+encoding commands.
 
 Enigmamachine is written using Sinatra, Thin, and Eventmachine.
 
@@ -51,19 +52,17 @@ receive the video. When the upload is complete, make an HTTP call something like
 
 with the params:
 
- params["video"] # the full path to a file on your local filesystem
- params["encoder_id"] # the id of an encoder defined in your database
+ "video=/foo/bar/blah.mp4" # the full path to a file on your local filesystem
+ "encoder_id=1" # the id of an encoder defined in your enigmamachine database
 
-The enigmamachine will run all encoding tasks on the video, while your web application will be free to continue serving requests happily.  If a second video
+The enigmamachine will run all encoding tasks on the video, while your web
+application will be free to continue serving requests happily.  If a second video
 is uploaded while the first one is still encoding, it will be placed in a queue.
 Videos are encoded sequentially as they arrive.
 
 All requests, whether they come from your browser or from your code, are
 protected by HTTP basic auth.  By default, the username is
-<i>admin</i> and the password is <i>admin</i>.  If you're accessing your
-Enigmamachine programatically, the server expects a Base64 encoded hash
-of the username and password, separated by a colon (":"), in a parameter
-called "HTTP_AUTHORIZATION".
+<i>admin</i> and the password is <i>admin</i>.  You can
 
 Programmatic requests in Ruby might look something like this:
 

data/VERSION

@@ -1 +1 @@
-0.3.1
+0.3.2

data/enigmamachine.gemspec

@@ -5,7 +5,7 @@
 
 Gem::Specification.new do |s|
   s.name = %q{enigmamachine}
-  s.version = "0.3.1"
+  s.version = "0.3.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["dave"]

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: enigmamachine
 version: !ruby/object:Gem::Version 
-  hash: 17
+  hash: 23
   prerelease: false
   segments: 
   - 0
   - 3
-  - 1
-  version: 0.3.1
+  - 2
+  version: 0.3.2
 platform: ruby
 authors: 
 - dave