Alpha Blue wrote: > First, I'm trying to do the legwork with utilizing all 4 together > because many people say it's a good combination to use.
It is. > I already have > apache setup (was using it with the PHP version of my site formerly). > > I've installed all gems and dependencies that I need on my slice (using > slicehost). Have you installed Passenger yet? And Ruby EE, if you'll be using that? > > I have a fully pushed git repository (master) on github (private git) > with one user. For sake of these questions the user on github is called > (liveuser). I followed the following guide to setup a user called > (gituser) on my slice: > > http://articles.slicehost.com/2009/5/13/capistrano-series-setting-up-git > > I just don't follow the logic of it. Perhaps it's because I don't > understand why I even need to use (any) of these utilities to run my > server. You don't need to. It just makes life easier. (And you're backsliding on those parentheses. They're not a subsitute for italics, unless you're writing in Turkish. :) ) > I feel like I have to perform 100 things just to get this > scenario working together. I'm sure it's nice when it's all setup and > working 100% but I'm a bit frustrated at this point. > > Question One: Is there a (complete guide) that acts as a walk-through > for setting up apache/capistrano/passenger/git together? There is a getting started guide on the Capistrano website. Have you looked at it? Apache and Passenger really don't come into the issue -- all you have to do is tell them where the code's going to be. > > From my understanding, capistrano is meant to be used only on the > development machine and not on the server. You deploy through git > directly to your server. I don't see any good documentation out there > that explains this in detail. If there were a deployment for dummies > book I'd buy it in a heartbeat. Ezra Zygmuntowicz has written such a book, but I don't know if it's still up to date. Anyway, what's the problem? Capistrano just automates the things you'd do yourself anyway. > > My Scenario: > > Windows Development machine with app > Full github private repository being pushed to from my development > machine > All tests well and am ready for deployment and production testing Why have you waited this long for deployment? You should (IMHO) have been doing a little at a time, all along. > Slicehost slice (server) with apache and passenger (passenger not setup > yet) Get Passenger set up next. > > Question Two: Is there an optimal setup here? What are the exact > steps, in order for deploying? Apache configuration first? Passenger > configuration first? Github configuration first? Get Passenger installed. Github needs no configuration. The order of the steps doesn't really matter that much. > > I will leave it at this for now. I'm sure I'm not the only one that has > pulled his or her hair out over a deployment phase and I'm certainly not > going to be the last. I think there should be some type of formalized > documentation on complete deployment (at least something that is up to > date and not 2 years old). There is. Check the Cap website. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
