Site management strategies with Subversion
Site management strategies with Subversion
- Subject: Site management strategies with Subversion
- From: email@hidden
- Date: Mon, 13 Mar 2006 12:25:50 -0800
Ok, since people seem to be ok with this topic of conversation (and I
thank everyone who has participated!), here's one more.
Something I do frequently is push small changes from a dev site to a
live site. In CVS I do this by tagging the files in the dev site I
want to move over with "stable", then going over to the live site
(which was originally created by checking out on the "stable" tag)
and doing a "cvs update". Voila.
I asked on the Subversion list how this same action would be
accomplished, since they don't have tags in the CVS sense. I
received several replies, which boiled down to this: create a tag,
which is really just a 'cheap copy' of the current state of the
repository, called /tags/stable (the /tags directory is optional, but
is a convention they recommend). Then each time I want to move
something to stable I would remove and recreate the stable copy, then
update the live site from it.
Although this would work, it isn't nearly as flexible as what I do
today with CVS. Because tags are applied on a per-file basis, I can
be committing work as I go along without fear of it showing up in the
live site; that won't happen until I explicitly tag it. In the
Subversion universe it appears that anything committed is going to be
going over the wall.
This has to be a common problem - how do the rest of you handle these
things?
Thanks once again,
janine
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden