> From what I understand, Capistrano is the tool that is used to deploy
> the application to your server. It has nothing to do with
> apache/passenger etc. correct?
99% correct. You can (and will) tell Capistrano how to restart your
webserver in order to pick up the latest deployed files (since Rails
won't check for new files in production).
For Apache/Passenger this just amounts to adding the following to your
deploy.rb file:
namespace :deploy do
desc "Restarts your application."
task :restart, :roles => :app, :except => { :no_release => true } do
as = fetch(:runner, "app")
via = fetch(:run_method, :sudo)
invoke_command "touch #{current_path}/tmp/restart.txt", :via =>
via, :as => as
end
end
> Secondly, passenger is a front-end piece and apache is the back-end
> piece of the server setup correct?
Sort of. Apache is the web server and is the *first* piece of
software to handle any requests coming from the client. Passenger is
an apache module that knows how to handle requests made to your Rails
app. So Passenger is like mod_php, but for Rails.
> If I didn't want to use passenger, I
> could use mongrel in it's place? Not saying I would do this but just
> clarifying for understanding..
Yes, you could. The Apache configuration would be a little bit
different, but you're right in that you either use Passenger or you
use Mongrel (or thin, etc.).
>
> In order of priority configurations:
>
> Apache first
> Passenger Second
> .. that handles the server end?
Yes.
> Is there documentation on setting up apache with rails? Prepping?
> Link
> please.
>
> Is there documentation on setting up passenger with apache? Prepping?
> Link please.
http://modrails.com/install.html
http://modrails.com/documentation/Users%20guide%20Apache.html
>
>
> How does capistrano tie in with git and my server? For instance, I
> see
> the following as an example configuration:
Seems you're missing the "deploy_to" line...
set :deploy_to, "/home/web/yourapp.com"
Google around and you'll find articles on how to get this working.
>
> I've read the documentation but it doesn't appear to talk about this.
> I'm not using Ruby EE by the way - just a heads up.
You don't need to. You can, but it's not necessary.
> I commented everything myself above to show you what I believe is
> happening. If I'm incorrect, please let me know. Let's bring this
> topic closer to capistrano usage first and I'll work with one piece
> and
> iron out the others after I get capistrano logic down.
http://articles.slicehost.com/2009/5/13/capistrano-series-setting-up-git
Also, if you're not, hop on the slicehost IRC chat... lots of helpful
people there doing exactly what you're doing...
-philip
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
