<div class='by' style='font-style: italic;'>by tlhIngan ( 30335 )</div>
<div class='comment_content'><p></p><p>> ... belongs behind ssh or, at least, behind http access and SSL.</p><p>> If I catch you doing otherwise for anything other than FOSS software I'll smack you. Hard.</p><p>And it probably is. The thing is, the website owners are using git to version control and deploy their website (not a bad idea). So they develop their web site, push it to the central git repo, and whenever they need to go live, they just do a "git pull" on the webserver and it'll pull down the latest version of the website.</p><p>Problem is, they forget about the hidden .git directory git makes that stores all sorts of useful information and with a little persistence, allow you access to the raw source code since you can access the individual git objects. (Or maybe even clone it using git).</p></div>
<div class='comment' style='display: block; margin-left: 80px'>
<div class='by' style='font-style: italic;'>by tlhIngan ( 30335 )</div>
<div class='comment_content'><p></p><p>> ... belongs behind ssh or, at least, behind http access and SSL.</p><p>> If I catch you doing otherwise for anything other than FOSS software I'll smack you. Hard.</p><p>And it probably is. The thing is, the website owners are using git to version control and deploy their website (not a bad idea). So they develop their web site, push it to the central git repo, and whenever they need to go live, they just do a "git pull" on the webserver and it'll pull down the latest version of the website.</p><p>Problem is, they forget about the hidden .git directory git makes that stores all sorts of useful information and with a little persistence, allow you access to the raw source code since you can access the individual git objects. (Or maybe even clone it using git).</p></div>
<div class='comment' style='display: block; margin-left: 80px'>