There are three ways of handling this, that I can think of.

1) Use a single common repository on a library machine, set up common directories on target machines and ssh trust relationships using the appropriate public keys. Keep your scripts in those common directories, with updates pushed out regularly from your library machine.

2) Use a single common repository on a library machine, and export a single directory of usable code as a NFS mount.

3) You could do what Mindspring used to do, which is use the apt package manager to package all their code, and then set up an internal repository. Then, synchronization would become:

apt-get update
apt-get upgrade

[download]
Update: if your code distributions would include large flat file database dumps, then I cannot recommend CVS as a distribution mechanism. I saw CVS being used once as a backup mechanism for flat file database dumps. By the time the dump reached a few hundred megabytes, it exceeded the memory of the target CVS machine and the backup was failing. Even scp would have been more robust with respect to size.

In reply to Re: Distributing code to 100's of servers by dwm042
in thread Distributing code to 100's of servers by perlofwisdom

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.