pastbedti.me » capistrano

Change PATH environment with Rails and Capistrano

Mathias Stjernström — Wed, 01 Jun 2011 20:09:49 +0000

Note to self.

When deploying my RubyOnRails applications with Capistrano and I get errors like this one

1
2
3
4
5

servers: ["app.myserver.com"]
[app.myserver.com] executing command
** [out :: app.myserver.com] sh: bundle: command not found
command finished in 31ms
servers: ["app.myserver.com"] [app.myserver.com] executing command ** [out :: app.myserver.com] sh: bundle: command not found command finished in 31ms

Capistrano executes the commands in a very basic shell so the $PATH environment are not the same as when you login through SSH.

One way to solve this is by setting PermitUserEnvironment to yes in /etc/sshd_config and then add the correct PATH to ~/.ssh/environment

I just found another way that was much easier

In you config/deploy.rb add the following snippet

1
2
3

set :default_environment, {
'PATH' => "/opt/ruby-enterprise/bin/:$PATH"
}

Thats it!

Cheers!

Handling a staging environment with capistrano / rails

Mathias Stjernström — Tue, 06 Jan 2009 20:49:06 +0000

Just before christmas I worked with one of our customers new server cluster or cloud if you may.
This cluster has production nodes and staging nodes and this post is about how to get capistrano to play nice with both production and the staging environment.

I have googled for a solution but all solutions I found where pretty ugly so i decided to create my own. When writing this line I did a test googling just to give an example of a bad example and my first result where the buckblogs blog. A post about a plugin called multistage I do not how I could miss that

But as my solution is so simple I will continue this post and show you anyway.

As usual I have written to much bullshit and I guess that you just want is some code so here you go.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

desc "Run tasks in production enviroment."
task :production do
# Production nodes
role :app, "192.168.1.30"
role :app, "192.168.2.30"
role :db, "192.168.1.30", :primary => true
end

desc "Run tasks in staging enviroment."
task :staging do
# Staging nodes
role :web, "192.168.1.60"
role :app, "192.168.2.60"
role :db, "192.168.1.60", :primary=>true
end

This is all there is to it. Splitting your role definitions into different tasks.
Now you may wonder how you use this when deploying or whatever you do.

Just add those tasks as params to cap.

1
2
3
4
5

cap staging deploy:check
cap staging deploy
# or
cap production deploy:check
cap production deploy

And here is a little bonus

Just to spice this up a bit I added another useful function. A little warning if you are about to deploy to your production environment. When running a big/important site you do not want to deploy into the wrong environment

This is how the final code looks.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

desc "Run tasks in production enviroment."
task :production do
# Prompt to make really sure we want to deploy into prouction
puts "\n\e[0;31m ######################################################################"
puts " #\n # Are you REALLY sure you want to deploy to production?"
puts " #\n # Enter y/N + enter to continue\n #"
puts " ######################################################################\e[0m\n"
proceed = STDIN.gets[0..0] rescue nil
exit unless proceed == 'y' || proceed == 'Y'

# Production nodes
role :app, "192.168.1.30"
role :app, "192.168.2.30"
role :db, "192.168.1.30", :primary => true
end

desc "Run tasks in staging enviroment."
task :staging do
# Staging nodes
role :web, "192.168.1.60"
role :app, "192.168.2.60"
role :db, "192.168.1.60", :primary=>true
end

When this code is used you will get something like the image below.

And thats all there is to it. The only thing that I think is missing is a warning/notice if you do not specify either production/staging. Like it is now you will get an error when capistrano cannot find any valid servers.

Happy deploying!

New version of capistrano_colors released.

Mathias Stjernström — Sun, 04 Jan 2009 15:36:40 +0000

Just released a new version of capistrano_colors. This is a total rewrite from the last version. This post show some of the bigger changes.

The biggest/coolest changes:

You can write your own custom machers and colorize rows that’s special for you.
I found a pretty neat way of making capistrano_colors system wide.
You can hide rows that you do not care for

I do not want to bore you more so I’ll just skip to an example

If you have not already, install capistrano_colors (v.0.5.0)

1	sudo gem install capistrano_colors

The following commands can go into deploy.rb or ~/.caprc depending if you want cc for a single project or system wide.

1
2
3
4
5
6
7
8
9
10

require 'capistrano_colors'

capistrano_color_matchers = [
{ :match => /command finished/, :color => :hide, :prio => 10 },
{ :match => /executing command/, :color => :blue, :prio => 10, :attribute => :underscore },
{ :match => /^transaction: commit$/, :color => :magenta, :prio => 10, :attribute => :blink },
{ :match => /git/, :color => :white, :prio => 20, :attribute => :reverse },
]

colorize( capistrano_color_matchers )

The only mandatory options are :match, :colors and :prio.

A fast description of the options:

:match – A regular expression of the row to match.

:color – The color we want on the matching rows.

:prio – What prio should this rule have (higher = more prio)

:attribute – Special effect (:underline, :reverse, :blink)

:level – Specify if this matcher should be bound to some of capistranos log levels (info,debug,…)

A more detailed description can be found at http://github.com/stjernstrom/capistrano_colors/tree/master

As this is a rewrite I would love some feedback.

Thanks!

Put some colors on your capistrano output

Mathias Stjernström — Sat, 20 Dec 2008 23:02:02 +0000

I got so tired of all the messy capistrano output so today I released my first public gem.

The name of the gem is capistrano_colors and the aim of the gem is to put some nice and shiny colors on capistrano output. The gem has only been tested with rails but should work wherever capistrano works.

Keep on reading to see some screenshots!

Just follow the instruction on the github page (http://github.com/stjernstrom/capistrano_colors/) and you will have a colorful output like the second screenshots in no time.

Capistrano output without capistrano_colors

Capistrano output with capistrano_colors

As you can see the output on the second image is much clearer and easier to understand.

Try it out and let me know what you think!

Cheers!