Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tense fix #184

Merged
merged 1 commit into from Apr 28, 2014
Merged

tense fix #184

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
16 changes: 8 additions & 8 deletions Readme.md
View file
Open in desktop
Expand Up @@ -7,7 +7,7 @@ generates an entire procedure as a Bash script and runs it remotely in the
server.

Compare this to the likes of Vlad or Capistrano, where each command
is ran separately on their own SSH sessions. Mina only creates *one* SSH
is run separately on their own SSH sessions. Mina only creates *one* SSH
session per deploy, minimizing the SSH connection overhead.

$ gem install mina
Expand Down Expand Up @@ -95,7 +95,7 @@ example, it provides the `mina restart` command.

The magic of Mina is in the new commands it gives you.

The `queue` command queues up Bash commands to be ran on the remote server.
The `queue` command queues up Bash commands to be run on the remote server.
If you invoke `mina restart`, it will invoke the task above and run the queued
commands on the remote server `your.server.com` via SSH.

Expand Down Expand Up @@ -155,7 +155,7 @@ end
~~~

In this example above, if you type `mina down`, it simply invokes the other
subtasks which queues up their commands. The commands will be ran after
subtasks which queues up their commands. The commands will be run after
everything.

Directory structure
Expand Down Expand Up @@ -193,7 +193,7 @@ set :repository, 'http://github.com/flipstack/flipstack.git'
task :deploy do
deploy do
# Put things that prepare the empty release folder here.
# Commands queued here will be ran on a new release directory.
# Commands queued here will be run on a new release directory.
invoke :'git:clone'
invoke :'bundle:install'

Expand Down Expand Up @@ -261,7 +261,7 @@ commands to restart the webserver process. Once this in complete, you're done!
### What about failure?

If it fails at any point, the release path will be deleted. If any commands are
queued using the `to :clean` block, they will be ran. It will be as if nothing
queued using the `to :clean` block, they will be run. It will be as if nothing
happened. Lets see what happens if a build fails:

$
Expand Down Expand Up @@ -393,9 +393,9 @@ Consider using `print_error` instead.
## Queueing

### queue
Queues code to be ran.
Queues code to be run.

This queues code to be ran to the current code bucket (defaults to `:default`).
This queues code to be run to the current code bucket (defaults to `:default`).
To get the things that have been queued, use commands[:default]

Returns nothing.
Expand Down Expand Up @@ -805,7 +805,7 @@ Any and all of these settings can be overriden in your `deploy.rb`.
Sets the Rails environment for `rake` and `rails` commands.

Note that changing this will NOT change the environment that your application
is ran in.
is run in.

### bundle_prefix
Prefix for Bundler commands. Often to something like `RAILS_ENV=production
Expand Down