Comments on: Automate Your Rails Deployment

By: Mr Frosti

Mr Frosti — Mon, 22 Sep 2008 22:32:29 +0000

Thanks for the mention - I just did a recent deployment using mod_rails in a slightly more complex setup involving multiple projects on the same DNS. A few hiccups later, I again had a successful (and solid) production environment with just a few clicks.

My only complaint with mod_rails currently is it doesn’t seem to be easy to setup a rails project as DocumentRoot, while having RailsBaseURI point to symlinks inside the root project’s public folder. I finally decided on different ports - less than ideal.

By: automate rails deploy and provisioning — award tour

automate rails deploy and provisioning — award tour — Tue, 19 Aug 2008 18:09:59 +0000

[...] Official CitrusByte Blog » Automate Your Rails Deployment. some interesting scripts for automating provisioning too. [...]

By: Mitchell Hashimoto

Mitchell Hashimoto — Sat, 16 Aug 2008 18:53:25 +0000

I suppose, but with the preference pane it sets up the vhost for you so that is a plus. And you can’t beat running your application components all at the same time, without having to worry about ports being taken up. I have client work, personal work, etc. all sitting idle all the time with my apache, so I just go to “somework.loc” in my browser and it boots up the rails process for me, without me having to terminal in and script/server it. Additionally, coding URLs to use “.loc” instead of “.com” is a lot easier than worrying about ports.

And if you just put this alias in your bashrc file:

alias prestart="touch tmp/restart.txt"

Then typing that instead of ^c then script/server and waiting for it to boot everytime is a great resource.

By: Daniel

Daniel — Fri, 15 Aug 2008 19:31:32 +0000

Because you still have to create a vhost directive for each site.

Process of passenger on OSX w/ Passenger preference:

1) Open up apple preferences
2) Drag rails directory to preference
3) Make alias to tmp/restart.txt

Lame!

By: Mitchell Hashimoto

Mitchell Hashimoto — Fri, 15 Aug 2008 03:50:04 +0000

Daniel, how is typing

script/server

easier than making an alias to touch tmp/restart.txt?

Another benefit for development is if you’re running multiple rails servers you can run all of them on port 80 at the same time, so you don’t have to play with port 3000, 3001, etc.

By: links for 2008-08-09 [delicious.com] « Amy G. Dala

links for 2008-08-09 [delicious.com] « Amy G. Dala — Sat, 09 Aug 2008 14:31:18 +0000

[...] Official CitrusByte Blog » Blog Archive » Automate Your Rails Deployment (tags: rails deployment reference) [...]

By: Daniel Fischer

Daniel Fischer — Thu, 07 Aug 2008 23:37:57 +0000

I am just starting to use passenger for my production environment.

I tried it for local development, but I don’t think that is the best application to use it. Typing out script/server is a lot easier.

By: Ari Lerner

Ari Lerner — Mon, 21 Jul 2008 22:57:06 +0000

The newest fixes (including a gem fix) have been pushed into the latest sprinkle release so:

gem install sprinkle

should work once again (thanks marcus)

By: Malko

Malko — Mon, 21 Jul 2008 22:55:26 +0000

Mitchell,

Thanks for this. Getting this setup on my slicehost was a breeze. I found one error that I can’t quite shake. It seems that none of my rubygems are taking hold. If I go into an irb prompt and do require ‘haml’ for instance, I’m getting errors that it doesn’t know how to load this. Now I know I can require ‘rubygems’ before hand, but do you have any idea how to solve this issue so that you don’t need that require ‘rubygems’ like it is on my local machine?

Thanks!

By: Mitchell Hashimoto

Mitchell Hashimoto — Sat, 19 Jul 2008 15:52:57 +0000

@Martin: You’re correct, Apache2 it is! Unfortunately I didn’t save an easy editable version of the image. But good catch.

@Alistair: Thank you! If you’re interested in slicehost you should follow my fork of Sprinkle at github:

http://github.com/mitchellh/sprinkle/tree/master

Sprinkle was made with provisioning slicehost specifically, though it can be used to sprinkle any time of server.