On Wed, 2003-05-14 at 08:57, Zieg, Mark wrote: > > I'd like to be able to checkout the dev module and make changes, then > > test them (which if I understand correctly takes a commit before the > > changes are uploaded to the repository) on the dev server, then if all > > goes well, have the appropriate files committed to the production > > server. Keep in mind that there would be two repositories each on > > different servers. I've seen the project CVSviaFTP, but don't want > > things to be committed to production until it's been tested in dev and > > explicitly flagged to be committed to production. I've heard this setup > > is complicated. > > Why do you want two repositories? It works MUCH easier, if at all possible, > to only have one repository (usually on the dev box), and have the > production box do an "update" from the dev box when a verified, tested tag > is available.
Mark, Thank for your response. I think I confused myself and am making it harder than it should be. Ok, so one repository it is, on the dev server. I think I understand how it should work, but please go easy on a newbie....just need a few things clarified. Ok, so I create the repository on dev. I checkout the module, make changes, update the module (commit the module/files???). Can someone explain the difference in an "update" and a "commit"? Say I have tested a change and am ready to move the code to the production server....what's the best way? Here's how I can think to get it from the dev repo to the prod box. Say the module is called "em" and is stored on the prod box in /home/kevin/em. I would do an initial checkout of the code on the dev repo. Then after a change was made to a file on the dev repo, I would do the following to get the changes to prod. 1) On the prod box, make the cwd /home/kevin/em. 2) Connect to the dev box via the pserver and checkout the em module. 3) I assume only the file(s) I've made changes to would be copied over. Is this correct? Any suggestions? Thanks so much for your help with this! Kevin -- Kevin Old <[EMAIL PROTECTED]> _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
