where are project files in remote repo in Git?

Question

I start to use Git and my project VCS. I have created a remote repo using

git init --bare

in /codes-repo and push changes from local repo to there. then I want to move project files from there to /var/www/project to be accessible for http://.... . but I don't see any project files (index.php,css/,....) at /codes-repo to copy them, there are only git files and folders there. Where are them??

score 4 · Accepted Answer · edited May 23 '17 at 12:27

4

A bare repository does not have a checkout. That is to say, a bare repository only holds the commit information - it does not keep a copy of the actual files on disk within the repository folder.

Bare repositories can only be pushed to or pulled from. To get a hold of the files, your best bet is probably to clone the bare repository (as a non-bare clone), and run a checkout at the clone.

Another option, if you're feeling brave, is to convert the bare repository into a non-bare repository (How do I convert a bare git repository into a normal one (in-place)?)

edited May 23 '17 at 12:27

Community

1
1

answered Dec 03 '12 at 11:22

Chamila Chulatunga

4,856
15
17

There are also git commands for extracting objects from the database. E.g. `git show`. – bames53 Dec 03 '12 at 17:54

miaout17 · Answer 2 · 2012-12-03T11:59:34.500

2

To copy the files from a bare repository, you can use git archive

GIT_DIR=~/BARE_REPO git archive --format tar master | tar xvf -

the git archive command will convert the target commit (marter, for example) to tar format, and send to the standard output. You can pipe it to a tar command to extract immediately.

Another way is just checkout the repository.

git checkout ~/BARE_REPO myproject

However, it's not suitable to put this whole directory into you web server. Otherwise your entire .git directory will be accessible. Anyone can get your source code and complete commit history (Of course, you can block these access by .htaccess or nginx setting).

edited Dec 03 '12 at 11:59

answered Dec 03 '12 at 11:28

miaout17

4,715
2
26
32

A bare repository doesn't have a .git directory, that's why it's called bare repository.# – dunni Dec 03 '12 at 11:56
Edited. It was a typo. Just point to the bare repository directory instead of .git directory. – miaout17 Dec 03 '12 at 12:00

score 1 · Answer 3 · answered Dec 03 '12 at 11:26

A bare repository doesn't have a so-called working directory, so won't have any filesystem objects.

Git still keeps track of contents, commits, tags and so on, but store them packed somewhere. When you git checkout in a nonbare repository, git updates the index (the files in the repository) to reflect the tree-ish object given as the argument.

where are project files in remote repo in Git?

3 Answers3

Linked