[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn enabled for a remote website

From: Todd Eddy <vrillusions_at_neo.rr.com>
Date: 2004-02-06 07:21:02 CET

Here's another "think tank" situation.

Ever since I've started to look at svn I've thought about making my
website svn enabled. Here are the issues though:

- website is hosted on a shared hosting plan, so can't install svn on
that server (probably could with enough hacking, but don't want the
limited ammount of space on have there eaten up by svn.
- svn is on the local network here on a computer that is connected
24/7 to an allways on internet connection.
- when modifing pages, I want to see the changes immediately if I
mess up something
- there were others that I can't think of right now

I've though of a couple ideas for this. Now this first one uses the
idea that you can pretty much read straight from the repository
folder without problems, which it sounds like you can. I would set
up an rsync connection between my computer here and the hosts server.
 when I start to modify stuff, I run a script that runs it every 1 or
2 minutes. Won't be that big of a deal since it only uploads what
changes, so most of the time it won't be doing anything. But I would
commit the changed file to the repository, which would then get on
the website within a couple minutes, which is an acceptable ammount
of time to wait.

The other method, which I would probably end up doing if I decide to
do it, is basically keeping the two separate. I would make changes
and upload them to the site, if it works right I'll commit the file
to the repository. Plus this would allow me to not have to put
everything in svn, and put all the items I do want to track in svn.
My main area of concern is the "reference" section, which has
writeups I do on various topics (working on a detailed how-to install
svn) and then maybe the section with all my style sheets and includes
and stuff. Neither area gets updated too frequently, so this upload
and then commit version would probably be more ideal in a situation
like this.

I know there is an svn powered wiki script out there, but I'm still
going to be the only person that adds or modifies files. I'm not
even sure if I'm going to do it, mainly just going to use svn for the
scripts I'm going to be making, not for web pages. This is just sort
of an after-thought thing that I thought some people would like to
brainstorm about if your waiting to get out of work friday :)

Todd Eddy
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 6 07:21:23 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.