title: Git: How to manage a website with Git? How to use Git for a website -deployment?
body: <p>Originally, I thought my problem was <code>How to maintain branches in Apache's DocumentRoots?</code> but realized the right question actually is <code>How to use Git to deploy stuff to web -server such as Apache?</code>.</p>
  
  <p>I feel I have understood now the DocumentRoot -problem, it would require Apache hacking that I want to avoid because much simpler solution using side-effects and putting the repo outside the deployment -dir but now a problem to understand git-fetch-hook and how to deploy stuff if the outside thing is a large dir, perhaps just cp besides and then mv -- but there must be some better way of syncing the deployment -dir, thinking.</p>
  
  <blockquote>
    <p><strong>DocumentRoot -problem</strong></p>
    
    <blockquote>
      <p>DocumentRoots specify the dirs in httpd.conf for hostable material.
      Now in such folder, I want ticgit -branches and feature -branches.
      When I create branches in some DocumentRoot, I get master and the
      other branch mixed up. <code>$ git checkout --orphan feature-0.01</code> is not
      empty but contains master -things. <code>$ ti new ...</code> creates a branch
      that has stuff from master, apparrently some bug in Ticgit (it works
      in small repos but creating ticgit -branch for larger repos like my
      DocumentRoot results into havoc). So how do you maintain your braches in Apache's DocumentRoot? Do you have your tickets there? 
      What about your feature -branches? Look I am puzzled by this, <code>$ git
      checkout feature-0.1</code> and now how does apache knows which files it
      should host? Things in master or things in <code>feature-0.1</code>?</p>
    </blockquote>
    
    <p><strong>My updated understanding of the DocumentRoot -problem</strong></p>
    
    <blockquote>
      <p>Now the problem with latter is that the deployment is not meant to
      work like this. I know SethRobertson's guide instructs some ways to
      use git for deployment. I think they are the best methods so far
      instead of hacking the Apache with git -repo inside the deployment
      -dir (commonly www).</p>
    </blockquote>
  </blockquote>