What you're planning -- allowing a junior webmaster to update a production server -- is frought with peril.
You can make it somewhat safer by providing the junior webmaster with a test environment that includes your script, running under the same web server. Require that he first test his "plugins" there.
To be even safer, arrange for the production server to not accept a plugin unless it's been (successfully) run on the test server. Have the test server generate a special hash of the plugin, use it as the upload password, and have the production server re-check the hash against the plugin, discarding the plugin if they don't match.
Digest::MD5 generates hashes. To prevent spoofing, append a known-to-the-system passphrase to the script before hashing.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.