On 9/6/06, Ryan Schmidt <email@example.com> wrote:
> On Sep 6, 2006, at 09:15, Timothy Madden wrote:
> > I will try rsync. Still overwriting all my images/ and jpeg/ folders,
> > even locally, might be a problem.
> but the point of rsync is to pull only the files that have actually
> changed... if all the images have changed, then surely you want all
> the images to be updated, and if only a few images have changed, then
> only those few images will be updated.
> > Having my working copy accessible by the web server will solve the
> > multiple developers problem,
> > but otherwise is like turning the public folder into a wc. My problem
> > is I have multiple aliases for
> > the public folder, one for each client, and each of them has its own
> > configuration. If I duplicate the
> > public folder into a number of working copies, the number of aliases
> > to maintain multiplies
> > accordingly. However I think this is what I will have to do when I
> > have some colleagues working
> > with me on my project.
> Again I don't understand why you would need to define an alias for
> each working copy. We certainly didn't. But then again I know nothing
> about IIS.
My problem is I work directly with the live server. We use a custom
language for server-side scripting, which keeps track of the clients
and requiers the aliases, and which we can not install on a
So I was thinking I could check out a working copy outside the web
server and continuously export and rsync as I develop the site and
need to see my changes. I would create a script to execute 'svn export
--force . /CleanSite/' and 'rsync' and run with a command from my
editor vim7.0, if only I could find a way to have the job done fast
enough. I was also thinking about using a RAM drive to hold
/CleanSite, because svn export --force will overwrite all my image
files, be they modified or not.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Sep 6 12:49:04 2006