in reply to Re: CVS and perl
in thread CVS and perl

For the moment we have a server and a db for alpha development. Everyone can develop on it and everyone can acces anyones files...

Then we got the production server with db.

For the moment we are setting up a beta test-environment.
My question is where does CVS fit in? For the moment I edit on the alpha server. When it works I drop it in production(soon step in between:beta). Do I need to keep editing on the alpha server and push it in the cvs?
Don't really understand how I can implement it. Got the rough idea on how and what it does... But with actual using it, I have no clue...


--
My opinions may have changed,
but not the fact that I am right

Replies are listed 'Best First'.
Re: Re: Re: CVS and perl
by arhuman (Vicar) on Apr 12, 2001 at 17:00 UTC

    For the moment we have a server and a db for alpha development.
    Everyone can develop on it and everyone can acces anyones files...
    Then we got the production server with db.

    As you seem to NOT have strong right-checking policy, here is my suggestion :

    Put the CVS server on the test server, use an 'autoexport feature' (triggered by the loginfo file)
    to maintain an exact working copy of your repository on your test server.
    I'd suggest to make modules based on directories. (to benefit of the 'autoexport')

    When everything is ok, all you'll have to do, is to 'scp' (you read well ! not 'ftp' !) the files to the prod server...

    "Only Bad Coders Badly Code In Perl" (OBC2IP)
[reply]

In Section Meditations