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.
Sincerely,
Eric Roberts
ColdFusion Developer
FitchRatings
eric.roberts@fitchratings.com
phone: 312-368-3101
mobile: 630-335-5772
fax: 312-368-3342
Ryan Schmidt
<subversion-2007b
@ryandesign.com> To
Eric.Roberts@fitchratings.com
06/11/2007 02:05 cc
PM users@subversion.tigris.org
Subject
Re: Promotion system (for lack of a
better term)
On Jun 11, 2007, at 13:36, Eric.Roberts@fitchratings.com wrote:
> I am looking for something (either software or a method of doing so
> in SVN)
> where I do all my development work, then commit that to the dev
> repository...then once i am happy with the changes commit that to
> the live
> repository. I can see having my live directory on my dev box also
> being
> checked out of the live repository...but can you have a directory
> that is
> checked out from 2 repositories? I already have repositories on my
> dev box
> and on my live server. I hope that made sense.
Why do you want to have two repositories?
I recommend you use separate repositories only for concepts which
really are separate from one another. For example, I have a
repository for my software source code, and another repository for my
music.
I recommend you have just a single repository, served from a machine
that's accessible to both your live and dev environments -- which
could be either the live or dev machine, or a third machine,
depending on your setup. You can manage the separate dev and live
environments by making one of these a branch.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
______________________________________________________________________
Confidentiality Notice: The information in this e-mail and any attachment(s) is confidential and for the use of the addressee(s) only. If you have received this e-mail in error, please delete this e-mail. Unauthorized use, reliance, disclosure or copying of the contents of this e-mail, or any similar action, is prohibited.
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
---------------------------------------------------------------------
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:14:43 2007