config.example.yml in cloud-crowd-0.2.0

- old
+ new
@@ -1,48 +1,44 @@
 # The URL where you're planning on running the central server/queue/database.
-:central_server:          http://localhost:9173
+:central_server:      http://localhost:9173
 
+# Set the maximum number of workers allowed per-node. Workers only run while 
+# there's work to be done. It's best to set 'max_workers' below the point where 
+# you'd start to swap or peg your CPU (as determined by experiment).
+:max_workers:         5
+
 # The storage back-end that you'd like to use for intermediate and final results
 # of processing. 's3' and 'filesystem' are supported. 'filesystem' should only
-# be used in development, or on single-machine installations.
-:storage:                 s3
+# be used in development, on single-machine installations, or networked drives.
+:storage:             s3
 
 # Please provide your AWS credentials for S3 storage of job output.
-:aws_access_key:          [your AWS access key]
-:aws_secret_key:          [your AWS secret access key]
+:aws_access_key:      [your AWS access key]
+:aws_secret_key:      [your AWS secret access key]
 
 # Choose an S3 bucket to store all CloudCrowd output, and decide if you'd like
 # to keep all resulting files on S3 private. If so, you'll receive authenticated
 # S3 URLs as job output, good for 24 hours. If left public, you'll get the
 # straight URLs to the files on S3.
-:s3_bucket:               [your CloudCrowd bucket]
-:use_s3_authentication:   no
+:s3_bucket:           [your CloudCrowd bucket]
+:s3_authentication:   no
 
+# If you're using the 'filesystem' storage, perhaps with an NFS share or
+# something similar, all files will be saved inside of the 'local_storage_path'.
+# The default value if left unspecified is '/tmp/cloud_crowd_storage'.
+:local_storage_path:  /tmp/cloud_crowd_storage
+
 # Use HTTP Basic Auth for all requests? (Includes all internal worker requests 
 # to the central server). If yes, specify the login and password that all 
 # requests must provide for authentication.
-:use_http_authentication: no
-:login:                   [your login name]
-:password:                [your password]
+:http_authentication: no
+:login:               [your login name]
+:password:            [your password]
 
 # By default, CloudCrowd looks for installed actions inside the 'actions'
 # subdirectory of this configuration folder. 'actions_path' allows you to load
 # additional actions from a location of your choice.
 # :actions_path: /path/to/actions
 
-# Set the following numbers to tweak the configuration of your worker daemons. 
-# Optimum results will depend on proportion of the Memory/CPU/IO bottlenecks
-# in your actions, the number of central servers you have running, and your
-# desired balance between latency and traffic.
-  
-# The number of workers that `crowd workers start` spins up.
-:num_workers:             3
-
-# The minimum number of seconds a worker waits between checking the job queue.
-:min_worker_wait:         1
-
-# The maximum number of seconds a worker waits between checking the job queue.
-:max_worker_wait:         5
-
 # The number of separate attempts that will be made to process an individual
 # work unit, before marking it as having failed.
-:work_unit_retries:       3
+:work_unit_retries:   3
\ No newline at end of file