Re: git repository in production release

From: Drew Northup <drew.northup@maine.edu>
Date: Oct 21, 2010, 12:39 UTC
Message-ID: <1287664757.24161.17.camel@drew-northup.unet.maine.edu>
In-Reply-To: <loom.20101021T140249-924@post.gmane.org>

On Thu, 2010-10-21 at 12:13 +0000, Jonas wrote:

Show 19 quoted lines

> Hi,
> 
> I am afraid this is a rather stupid question, but I have spent quite some time
> to figure it out without any success.
> 
> 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. 
> When I run cap deploy Capistrano makes a new release and makes a new 
> directory under releases from the repository, I guess this is standard.
> 
> 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?

Why is this a git problem and not a Capistrano problem?

-- 
-Drew Northup
________________________________________________
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59