From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Jerome Yanga <jerome.yanga@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git push from client is not updating files on server
Date: Tue, 06 Mar 2012 20:34:46 -0600 [thread overview]
Message-ID: <4F56C946.8080601@gmail.com> (raw)
In-Reply-To: <CAC0z1F9sBYCuv_HMCx1ryWLvxZKUcLPS1UUj80ihEesje+SKzg@mail.gmail.com>
On 3/6/2012 6:28 PM, Jerome Yanga wrote:
> The project in Apache's DocumentRoot was created using the following command:
>
> "cd /var/www/git
> git clone --bare<non-bare working directory> <project>.git"
>
> Hence, I believe that is is bare. Besides, it does not have .git
> folder.
The bare repo is the .git folder. That's why its called barerepo.git.
.git = git repo. worktree/.git = non-bare repo with worktree and .git
repo. barerepo.git = bare repo and no worktree.
> I assumed that when I did this that the non-bare directory
> will also be updated when a push is performed via http.
>
The non-bare you cloned from is independent. It doesn't know about the
bare repo you cloned from it, and your bare repo does not know about the
non-bare repo it was cloned from. I'm not sure what you were doing with
that non-bare before you created the bare from it. You may not need
that non-bare anymore if that's all it was for.
> My objective is that I would like the developers to be able to push
> via http and these pushes will need to be reflected on the non-bare
> working directory as these directories will be used for automated
> tests.
>
Create a new non-bare clone of your bare repo. Then do git-pull on the
new non-bare after the bare gets updates (someone does git push to it)
and you want to test those new commits. The worktree of the new
non-bare clone can be the document root of your testing virtual host, if
that's what you're doing. That way, you know that no one else is
messing with new non-bare (test repo) like doing development in it and
messing up your tests.
v/r,
neal
next prev parent reply other threads:[~2012-03-07 2:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 16:52 git push from client is not updating files on server Jerome Yanga
2012-03-06 17:46 ` Ben Tebulin
2012-03-06 19:35 ` Junio C Hamano
[not found] ` <CAC0z1F-Eg2DOLvd3aA5XCoEJjj1jC=VWVkTA+uc24=18h3pN7g@mail.gmail.com>
2012-03-06 20:37 ` Junio C Hamano
2012-03-06 21:12 ` Neal Kreitzinger
2012-03-06 21:21 ` Neal Kreitzinger
[not found] ` <CAC0z1F_eyMo4D8E2j15dOFhp-6tZ_ixacB6XcKfNpJategcsXQ@mail.gmail.com>
[not found] ` <CAC0z1F_LYRkReO1qqcjkWy6Vb3E0_oNo-0kSf15nGfQFAtXpdg@mail.gmail.com>
2012-03-06 23:07 ` Jerome Yanga
2012-03-06 23:32 ` Neal Kreitzinger
2012-03-07 0:28 ` Jerome Yanga
2012-03-07 1:11 ` Neal Kreitzinger
2012-03-07 2:23 ` Junio C Hamano
2012-03-07 2:34 ` Neal Kreitzinger [this message]
2012-03-07 11:04 ` Holger Hellmuth
2012-03-07 15:43 ` Jerome Yanga
2012-03-30 18:23 ` Jerome Yanga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F56C946.8080601@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=git@vger.kernel.org \
--cc=jerome.yanga@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).