couchrest_model/bin/couchview

112 lines
3.2 KiB
Text
Raw Normal View History

2008-06-01 20:21:21 +02:00
#!/usr/bin/env ruby
2008-08-03 20:34:09 +02:00
commands = %w{push generate}
2008-06-01 20:21:21 +02:00
command = ARGV[0]
if !commands.include?(command)
puts <<-USAGE
2008-08-03 20:34:09 +02:00
Couchview has two modes: push and generate. Run couchview push or couchview generate for usage documentation.
2008-06-01 20:21:21 +02:00
USAGE
exit
end
if ARGV.length == 1
case command
2008-08-03 20:34:09 +02:00
when "generate"
puts <<-GEN
2008-08-03 21:51:17 +02:00
Usage: couchview generate directory design1 design2 design3 ...
2008-06-01 20:21:21 +02:00
2008-08-03 21:51:17 +02:00
Couchview will create directories and example views for the design documents you specify.
2008-08-03 20:34:09 +02:00
GEN
2008-06-01 20:21:21 +02:00
when "push"
puts <<-PUSH
2008-08-03 20:34:09 +02:00
== Pushing views with Couchview ==
Usage: couchview push directory dbname
Couchview expects a specific filesystem layout for your CouchDB views (see
example below). It also supports advanced features like inlining of library
code (so you can keep DRY) as well as avoiding unnecessary document
modification.
Couchview also solves a problem with CouchDB's view API, which only provides
access to the final reduce side of any views which have both a map and a
reduce function defined. The intermediate map results are often useful for
development and production. CouchDB is smart enough to reuse map indexes for
functions duplicated across views within the same design document.
For views with a reduce function defined, Couchview creates both a reduce view
and a map-only view, so that you can browse and query the map side as well as
the reduction, with no performance penalty.
== Example ==
couchview push foo-project/bar-views baz-database
2008-06-01 20:21:21 +02:00
2008-08-03 20:34:09 +02:00
This will push the views defined in foo-project/bar-views into a database
called baz-database. Couchview expects the views to be defined in files with
names like:
2008-06-01 20:21:21 +02:00
2008-08-03 20:34:09 +02:00
foo-project/bar-views/my-design/viewname-map.js
foo-project/bar-views/my-design/viewname-reduce.js
foo-project/bar-views/my-design/noreduce-map.js
2008-06-01 20:21:21 +02:00
2008-08-03 20:34:09 +02:00
Pushed to => http://localhost:5984/baz-database/_design/my-design
2008-06-01 20:21:21 +02:00
2008-08-03 20:34:09 +02:00
And the design document:
2008-06-01 20:21:21 +02:00
{
"views" : {
2008-08-03 20:34:09 +02:00
"viewname-map" : {
2008-06-01 20:21:21 +02:00
"map" : "### contents of view-name-map.js ###"
},
2008-08-03 20:34:09 +02:00
"viewname-reduce" : {
2008-06-01 20:21:21 +02:00
"map" : "### contents of view-name-map.js ###",
"reduce" : "### contents of view-name-reduce.js ###"
},
2008-08-03 20:34:09 +02:00
"noreduce-map" : {
"map" : "### contents of noreduce-map.js ###"
}
2008-06-01 20:21:21 +02:00
}
}
2008-08-03 20:34:09 +02:00
Couchview will create a design document for each subdirectory of the views
directory specified on the command line.
== Library Inlining ==
Couchview can optionally inline library code into your views so you only have
to maintain it in one place. It looks for any files named lib.* in your
design-doc directory (for doc specific libs) and in the parent views directory
(for project global libs). These libraries are only inserted into views which
include the text
//include-lib
or
#include-lib
Couchview is a result of scratching my own itch. I'd be happy to make it more
general, so please contact me at jchris@grabb.it if you'd like to see anything
added or changed.
2008-06-01 20:21:21 +02:00
PUSH
end
exit
end
2008-08-03 20:34:09 +02:00
require 'rubygems'
require 'couchrest'
if command == 'push'
dirname = ARGV[1]
dbname = ARGV[2]
fm = CouchRest::FileManager.new(dbname)
2008-08-03 21:51:17 +02:00
fm.loud = true
puts "Pushing views from directory #{dirname} to database #{fm.db}"
2008-08-03 20:34:09 +02:00
fm.push_views(dirname)
2008-08-03 21:51:17 +02:00
elsif command == 'generate'
puts "Under construction ;)"
2008-06-01 21:23:04 +02:00
end