Thanks guys,will give the suggestions a try.


On 2 July, 19:31, Jamis Buck <[email protected]> wrote:
> There is also a :none SCM that you can use. However, it only works
> with the :copy deployment method that Lee mentioned.
>
> So:
>
>   set :repository, "."
>   set :scm, :none
>   set :deploy_via, :copy
>
> You can read more about the :none SCM in the comments for that module:
>
> http://github.com/capistrano/capistrano/blob/e8429b0e198d3dbff53853e3...
>
> - Jamis
>
>
>
> On Thu, Jul 2, 2009 at 12:29 PM, Lee Hambley<[email protected]> wrote:
> > There is also the deploy_via :copy that will tar up your working directory
> > and deploy it to the server, you can read more about that on our wiki under
> > "Understanding deployment strategies"
> > - Lee
>
> > 2009/7/2 Joe McDonagh <[email protected]>
>
> >> sixones wrote:
> >> > Hello,
>
> >> > I've seen this question pop up a few times but haven't been able to
> >> > find a clear answer. Is there away to deploy with Capistrano without
> >> > using SCM? I like the idea of the automated deployment strategies
> >> > available with Capistrano and would like to benefit rather than
> >> > manually uploading via SFTP etc..
>
> >> > I fully understand how important SCM is but I'm planning on using
> >> > Capistrano to deploy binary builds to a remote server. Storing the
> >> > builds inside a repository just doesn't make sense for obvious
> >> > reasons.
>
> >> > Thanks in advance
>
> >> There is a 'put' method that uses scp to transfer files. You can make a
> >> task that uses this method to upload binaries.
>
> >> --
> >> Joe McDonagh
> >> Operations Engineer
> >>www.colonfail.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Capistrano" 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.co.uk/group/capistrano?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to