deployment - Is it ok to maintain a website as the Git master not a bare repo? -

deployment - Is it ok to maintain a website as the Git master not a bare repo? -

i have seen quite few entries using bare git repos above document root , hooks force deploy websites need maintain changes made website host , pull changes local copy. because installed prestashop cms using host's 1-click install manages minor updates, clones , backup restores useful. force deploy hooks assumes have master offsite approach seems upside downwards need. because of mysql db it's not handy maintain master locally, on bitbucket or without fiddling about.

my plan to.. (from www/subfolder)

$> git --git-dir=../../git/prestashop.git --work-tree=. init

but haven't done before or read else has. safe way manage production site? .git files wouldn't public , pull changes rather force them , utilize ssh issue git commands.

or if go flow , utilize bare repo method possible maintain hosts minor software updates prestashop?

i'm new tracking, still little gitslexic , used old school ftp workflow advice welcome.

i prefer have repo in separate directory , rsync or similar production directory, although have used git directories straight you're considering it, without real trouble. issue i've run when configuration file gets repo , replaces production configuration dev. can avoided .gitignore or similar though.

git deployment