I want
to have configurate a GIT repo for a website.
Multiple users will have a clone of the repo on their local machine and on the
end of each day they push their work
to the server. I can setup a bare repo, but I want a working dir/non-bare repository.
The idea is that the working dir of the repository will the root folder for the website. At the
end of each day all changes will be visible directly. But I can't find a way
to do this.
Initializing the server repo with git init gives the following error when a client is trying
to push some files:
git push origin master
[email protected]'s password:
Counting objects: 3, done.
Writing objects: 100% (3/3), 227 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: error: refusing
to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard'
to match
remote: error: the work tree
to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration variable
to
remote: error: 'ignore' or 'warn' in the remote repository
to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged
to update its work tree
to match what you pushed in some
remote: error: other way.
remote: error:
remote: error:
To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable
to 'refuse'.
To ssh://
[email protected]/home/orangetux/www/
! [remote rejected] master -> master (branch is currently checked out)
error: failed
to push some refs
to 'ssh://
[email protected]/home/orangetux/www/'
So I'm wondering if this the right way
to setup a GIT repo for a website?
If so, how do I have
to do this? If not, what is a better way
to setup a GIT repo for the development of a website?
EDIT
you can't push
to a non-bare repository
Oke, clear. But whats the way
to solve my problem? Create a bare repository on the server and have a clone of this repo on the same server in the htdocs folder? This looks a bit clumsy
to me.
To see the result of a commit I've
to clone the repository each time.
