Jeb,

That is a copy of the git repository for your project that gets
created with each release.  Checkout the deploy method that you're
using (deploy_via) which defaults to using 'git clone'  which will
copy the entire repo history.  You might try using "shallow clone",
see this page for more info: http://help.github.com/capistrano/

Hope this helps

Cheers,
-Tim Stackhouse

We can only see a short distance ahead, but we can see plenty there
that needs to be done.  --Alan Turing, 1950



On Thu, Oct 21, 2010 at 9:35 AM, jeb <[email protected]> wrote:
> Hi,
>
> I am afraid this is a rather stupid question, but I have spent quite
> some time to figure it out without any
> success. Nor do I know if this is a git och capistrano issue.
>
> I use git in my Ruby on Rails applications. On my deployment server
> there is a git directory that I push to
> in the admin users directory, Capistrano then puts the files in my
> webserver directory... Standard I guess.
>
> My releases are getting bigger and bigger, it takes longer and longer
> time for the cap deploy command to
> finish and the backups contain a huge number of files.
>
> What puzzels me is that in every release  there is a .git directory.
> As far as I can see it makes no use there,
> just takes up much space. Is it supposed to be like this or have I
> made a mess?
>
> How can I get rid of the .git directory in the deployment releases?
>
> :-) j
>
> --
> * 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.com/group/capistrano?hl=en

-- 
* 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.com/group/capistrano?hl=en

Reply via email to