Permalink
Browse files

an exorcism of tabs

  • Loading branch information...
1 parent e50f41b commit 9ec696b006fdfa57cf3f8af62bd902b94066086f @jashkenas jashkenas committed Sep 16, 2009
Showing with 13 additions and 13 deletions.
  1. +4 −4 README
  2. +4 −4 TODO
  3. +5 −5 views/index.erb
View
@@ -63,10 +63,10 @@
# Edit the configuration files to your satisfaction, add AWS credentials,
# and then load the CloudCrowd schema into your configured database.
- >> cd ~/config/cloud-crowd
+ >> cd ~/config/cloud-crowd
>> mate config.yml
>> mate database.yml
- >> [create the database you just configured...]
+ >> [create the database you just configured...]
>> crowd load_schema
# Write your actions, and install them into the 'actions' subdirectory.
@@ -78,15 +78,15 @@
>> crowd server
# The configuration folder also includes 'config.ru', which can be used by
- # any Rack-compliant webserver to run your central server.
+ # any Rack-compliant webserver to run your central server.
# Then, to launch a node of workers:
>> crowd node
# To spin up remote nodes, install the 'cloud-crowd' gem and copy over
# your configuration directory. Run `crowd node`, and the remote machines
- # will register with the central server, becoming available for processing.
+ # will register with the central server, becoming available for processing.
# At this point you can visit your Operations Center at localhost:9173 to
# view all of your nodes, ready for action.
View
@@ -1,9 +1,9 @@
TODO:
* Use the email field to send mail when the Job's gone bad.
* Job creation UI. Pick an action, add inputs, set options, go.
- * Think about adding a CLEANUP state, with WorkUnits being dispatched to
- workers to clean up a Job's leftover files on S3, instead of the current
- in-request cleanup. (see Job#cleanup_assets)
+ * Think about adding a CLEANUP state, with WorkUnits being dispatched to
+ workers to clean up a Job's leftover files on S3, instead of the current
+ in-request cleanup. (see Job#cleanup_assets)
* Look into Grand Central Dispatch for ideas about how to implement
Job ordering/piping around.
@@ -26,4 +26,4 @@ DONE:
* Basic integration tests.
* Unit tests for lib.
* Bump to version 0.1 and release on RubyForge.
- * Re-architected to use real Nodes (version 0.2).
+ * Re-architected to use real Nodes (version 0.2).
View
@@ -55,11 +55,11 @@
</div>
<div class="graph_container">
<div class="graph_title">
- Active Nodes
- (<span id="nodes_legend" class="legend_box"></span>)
- and Workers
- (<span id="workers_legend" class="legend_box"></span>)
- </div>
+ Active Nodes
+ (<span id="nodes_legend" class="legend_box"></span>)
+ and Workers
+ (<span id="workers_legend" class="legend_box"></span>)
+ </div>
<div id="workers_graph" class="graph"></div>
</div>
</div>

0 comments on commit 9ec696b

Please sign in to comment.