no server 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?

files can be pushed, of course, along with scripts running whatever we
might want along with the update, right?

On Fri, Feb 6, 2009 at 11:43 PM, Jamis Buck <[email protected]> wrote:
>
> On Fri, Feb 6, 2009 at 7:13 AM, Mathieu Jobin <[email protected]> wrote:
>> I am curious to know if anybody else thought of using Capistrano
>> before for other things than subversion-based-web-application-code ?
>> Whats your thoughts on this?
>
> Capistrano is definitely suitable for this. There are a lot of people
> using Capistrano for all kinds of creative, non-deployment scenarios.
>
>> I am guessing there is already a security check in place to verify the
>> identify of the server pushing the update? We'd like to see it has
>> having some kind of capistrano master server pushing updates onto our
>> other linux servers.
>
> Not sure what you mean by "security check"? Do you mean, something to
> prevent Capistrano commands from executing unless the remote IP
> address is in some whitelist? If that's what you mean, then no,
> Capistrano does not have anything like that. (Capistrano is enitrely
> client-side; there is no server-side component to Capistrano.) My
> SSH-fu is weak, but maybe there's a way to configure sshd to only
> allow connections from specific IP addresses?
>
>> we have many linux servers and many shares common roles and
>> configuration. so we would like to define our patchsets in a way that
>> match our needs.
>
> If you wind up using Capistrano for this, let us know. It sounds like
> a great application of cap.
>
> - 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to