Pål Bergström wrote: > Marnen Laibow-Koser wrote: >> Pål Bergström wrote: > >> Generally not. Capistrano will check out a working cooy to run on the >> server. You probably could run the app right from the repository, but I >> see no advantage and many potential problems in doing so. > > And now I'm lost. What's the repository for on the server?
The repository is a central place to store your Git data for your project. This is a Git concept (actually, it's a general version control concept). > And how is > that connected to the particular app root (I'm adding several domains > and apps under one main domain)? It's not connected in any particular way. The repository has to do only with source control, and does not know anything directly about deployment. > > When I use git locally, it's the same. I think. I only use git for > version control and using the branch command for testing new things. The > important thing for me is the local version. That's right. And likewise on the server: Capistrano will check out a local copy from the repository to be the actual running app instance. > The server is just to be a > mirror of that. That's a *very* simplistic way of looking at it. I'd say more that your local copy is a mirror of the server. Really, what's the problem here? There is a repository. From it, you check out copies for development, and Capistrano checks out copies (in the same way) for deployment. How much simpler can it get? :) 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 -~----------~----~----~----~------~----~------~--~---
