From f0f011245adaa4679fc96e0a40973071d358f8e8 Mon Sep 17 00:00:00 2001 From: Andrs Montaez Date: Thu, 24 Nov 2011 19:42:01 -0200 Subject: [PATCH] Readme tweaks. --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 34b0728..2c8612f 100644 --- a/README.md +++ b/README.md @@ -26,16 +26,18 @@ $ mage deploy to:production Easy boy. It's not sorcery, just some *technomagick*! In Magallanes you define environments like *testing*, *staging*, or *production* like on the example above. -Then, on that environment you can configure a set up specifing to which hosts you want to deploy and what tasks to run (*after*, *on*, and *before* deploying). +Then, on that environment, you can configure a setup specifing to which hosts you want to deploy and what tasks to run (*after*, *on*, and *before* deploying). +And you are done! -### And what spells... TASKS! What tasks has it built in? ### +### And what spells... tasks! What tasks has it built in? ### Just a few, for now... - **deployment/rsync** - This task is for deploying your code to the remote servers. - **scm/update** - This task is for updating (git/svn) your base wokring copy. -But! You can create your own taks, and execute commands on your working copy and in your deployed code! +But that's not all! You can create your own taks, and execute commands on your working copy and in your deployed code! +Also we are working on creating more built in tasks. ### This is awesome! Where can I learn more? ###