to my understanding then ... if I would have to put capistrano in a client-server relation, there would be only a server part, the capistrano "patchsets definition" and there is no capistrano clients part needed, only sshd.
and If I need to know what did I push by capistrano before on a specific client, I need to make my own system to track capistrano pushes. like a series of lock file, or a query-able history file of some sort. makes sense to you? On Sat, Feb 7, 2009 at 9:35 AM, Jamis Buck <[email protected]> wrote: > > On Fri, Feb 6, 2009 at 10:00 PM, Mathieu Jobin <[email protected]> wrote: >> >> no server side? > > Right, the server side is just sshd. Capistrano is simply a tool for > executing commands on remote hosts via SSH. It doesn't need any other > software on the remote side. > >> well, in this case, the developer working copy could be consider the >> master, which push the new release onto all capistrano clients, is >> that right? > > Sure. > >> files can be pushed, of course, along with scripts running whatever we >> might want along with the update, right? > > Yup. > > - Jamis > > > > -- the obvious is the prejudice. l'évidence est un préjugé. 明白な事が偏見です --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
