StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>@Michael, I disagree - I would say it's better to install on the linux vps, especially if you are already paying for the hosting service. I find it very helpful to be able to browse and download stuff from my svn repo wherever I am, from whatever computer I'm on.</p> <p>@nicky, I started with svn (and version control) several years ago and I took baby steps which made it easier to tackle. </p> <p>If I had to do it over again, I'd read the <a href="http://svnbook.red-bean.com/" rel="nofollow noreferrer">svn book</a> to start with. The book is very well laid out and didn't take more than 1-2 days to plow thru. </p> <p>While you're reading, install svn on your linux vps with an <a href="http://www.howtoforge.com/apache_subversion_repository" rel="nofollow noreferrer">apache front end</a>.</p> <p>Once you have that up, pick one of your websites and import it into svn. This is how I structure my svn repo. For example, say my repo is hosted at <a href="http://mysvn.mydomain.com/svn/" rel="nofollow noreferrer">http://mysvn.mydomain.com/svn/</a>:</p> <pre><code> mywebsite1 - trunk - tags - branches mywebsite2 - trunk - tags - branches </code></pre> <p>Don't worry about creating the perfect structure. It's pretty easy to re-organize especially when you're starting out. After you import a few projects into svn, you'll start to get a feel for which projects should have their own "trunk/tags/branches" dir structure and which can be combined. </p> <p>For creating test environments, I do exactly what you describe. I use build scripts to checkout from svn and download files into dirs that are mapped to subdomains like "test.clientsite.com" (I work primarily in java and use ant and maven, but I think you can use whatever scripting language you're familiar with).</p> <p>Once you get used to version control, you'll never go back, good luck!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload