threads / discuss / 25494

git repository in production release

Subject: git repository in production release

## tl;dr

4 messages between Oct 21, 2010 and Oct 21, 2010.

replies: 3people: 3as markdown or json

Jonas· Oct 21, 2010, 12:13 UTC · lore

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?

:-) j

Drew Northup· Oct 21, 2010, 12:39 UTC · re: Jonas · lore

Re: git repository in production release

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

Jonas· Oct 21, 2010, 14:03 UTC · re: Drew Northup · lore

Re: git repository in production release

Because I suspect that the local .git directory in my rails application folder should not be added to the remote repository at all. But I might be wrong.

Enrico Weigelt· Oct 21, 2010, 19:07 UTC · re: Jonas · lore

Re: git repository in production release

* Jonas <jonas@ibiz.se> wrote:

> Because I suspect that the local .git directory in my rails application 
> folder should not be added to the 
> remote repository at all. But I might be wrong.

Your repository (aka: the committed trees inside it) contain a .git directory ? That's very strange, should not happen in normal git operations (would cause some infinite recursion ;-o).

Seems that something's wrong w/ Capistrano - most likely not a problem of git itself.

cu

-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------