title: Best practice for structure of Subversion repository working copy?
body: <p>I'm just getting started learning how to use Subversion for building my web applications, so bear with me.</p>
  
  <p>Here is how I am setting it all up:</p>
  
  <ul>
  <li>One of my domains will host the repositories for all of my projects. I have the standard tags/branches/trunk structure. This is in a public folder so it can be accessed by other developers.</li>
  <li>I will have a folder on my live server containing each release of the application, and I'll have a symlink in the web directory pointing to the current release. This way, when I release an update to the application, I export it to the release directory and then switch the symlink so the changes are online instantaneously.</li>
  </ul>
  
  <p>Here is my question:</p>
  
  <p>What is the best structure for the local working copy of the project? I'm going to be working on both branches and the trunk quite frequently, so should I check out the entire repository structure (tags/trunk/branches) or just check out the trunk and each branch individually into different folders?</p>
  
  <p>Also, if anything I said about how I have it set up seems strange or a wrong way to do it, let me know (I'm new to this!).</p>