I am in the process of converting a large set of FTP shell scripts into a unified Perl system. The final product will use the Net::FTP module, and will keep login credentials, paths, and filenames in a separate config file (chmod 0600 or secured some other way). It will also call optional pre and post-processes, and keep a simple tied hash file (NDBM_File or some such) of previously downloaded filenames, sizes, and timestamps.

The key ingredients that let me sell this as a Perl project were the ability to use Net::FTP to get a directory listing and branch based on the results before QUIT-ing the ftp session, using Perl's native text processing for compliance-checking data, and using a simple database file to check for possible duplicate data. All those features have to stay in the final product, which makes me wonder how many more additional "cool" features I'll find myself unable to live without.

Im interested in seeing, before I go too far in a direction I'll regret later, how other coders have approached similar projects. Did the end product work out well? Was there a critical module that was a must-have? Did it end up a bloated nightmare that everyone hated? Did Master Foo enlighten you with a simple time-saving process that saved the day?

Thanks.

In reply to Perl-ifying bloated ftp scripts by delirium

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.