forked from documentcloud/cloud-crowd
/
README
75 lines (47 loc) · 3.23 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
_ _
( ` )_
( ) `)
(_ (_ . _) _)
_
( )
_ . ( ` ) . )
( _ )_ (_, _( ,_)_)
(_ _(_ ,)
_ _ ___ _ _ ___ _
( ` )_ / __| |___ _ _ __| |/ __|_ _ _____ __ ____| |
( ) `) | (__| / _ \ || / _` | (__| '_/ _ \ V V / _` |
(_ (_ . _) _) \___|_\___/\_,_\__,_|\___|_| \___/\_/\_/\__,_|
_
( )
_, _ . ( ` ) . )
( ( _ )_ (_, _( ,_)_)
(_(_ _(_ ,)
~ CloudCrowd ~
* A batch-processing system, map-reduce style
* Write your scripts in Ruby
* Built for Amazon EC2 and S3
* split -> process -> merge
* As easy as `gem install cloud-crowd`
~ Getting started ~
# Install the gem (documentcloud-cloud-crowd until the first official release).
>> sudo gem install cloud-crowd
# Install the CloudCrowd configuration files to a location of your choosing.
>> crowd install /etc/cloud-crowd
# Now, you can use the full complement of `crowd` commands from inside of
# this configuration directory. To see the available commands:
>> crowd --help
# Edit the configuration files to your satisfaction, and add AWS credentials.
>> mate /etc/cloud-crowd/config.yml
>> mate /etc/cloud-cloud/database.yml
# Write your actions, and install them into the 'actions' subdirectory.
# CloudCrowd comes with some default actions as an example.
# To spin up the central server (make sure that you include its location
# in config.yml), either:
>> crowd server
# or:
>> thin -R config.ru --servers 3 -e production start
# Any server that supports Rack should work with the rackup file.
# Then, to spin up 10 workers:
>> crowd workers start -n 10
# To spin up workers remotely, install the 'cloud-crowd' gem, and copy over
# your configuration directory.