On Jun 11, 2007, at 14:17, Eric.Roberts@fitchratings.com wrote:
> I have thought about that as well...the way I currently have it set
> up is
> on the dev box, when I commit changes from my local development
> directory,
> using the post commit hooks...it updates the dev box's live directory.
> What i want to be able to do is when i am happy with the change I
> made...promote them to he production server. I could just have the
> live
> directory on the production server be a check out of the repository
> on the
> dev box... My only concern is that if my partner has to work on
> something
> and for whatever reason, my dev box is not available (it's located
> in my
> home office and we have been known to lose internet access due to
> storms
> from time to time) that he be able to check out the latest version (or
> update to the latest version) from the live repository...hence the 2
> repositories....just a little redundancy. If there is a way to
> update the
> production repository from the live directory on dev while still
> having the
> live directory on dev as a checked directory from the dev
> repository...that
> would be ideal.
Again, this sounds like an unnecessarily complicated and fragile
setup. Just use a single repository, hosted from a location that's
available to all developers and to the live production server. Maybe
that means you should host it on the live production server itself,
since that's theoretically always available. Develop in trunk, and
when you have things you want to move to production, copy the trunk
to a new branch. Or, merge from trunk to an always-present
"production" branch. Or something.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 11 21:55:45 2007