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)

In reply to Re: Re: Re: CVS and perl by arhuman
in thread CVS and perl by toadi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.