I can't agree more with Abigail-II. Moreover, Production Environment being the most sensitive as well as the most critical.
I have been in the same situation before, and have realised that it is better to device your own plans other than postponing things because of insufficient privileges (like adminsterating, access levels etc.)
I'll let you know my thoughts ... and feel free to reply with any questions.
Here's my opinion:
  1. Leave the development area alone. Let the developers do whatever they want to. That region is of least importance with respect to your external customers/clients
  2. Have two test-bed environments (at least a minimum of one). One say 'User Acceptance' and the other 'Demo' (Pre-Production). The Demo should be exactly similiar (in terms of OS, Scripts, security levels etc.) to PROD.
  3. Make sure your code goes to Prod ONLY if UA and Demo are fine. Otherwise, start all over again
  4. Take a copy of your scripts in production to a location where only you (and whoever concerned) have access to - say 'prodbackup'. Update this directory every time there is a production move.
  5. You might also want to consider comparing files in 'prodbackup' with the ones in prod, so as to maintain consistency in the files.

That's just the beginning. Once you have some kind of process in place, there are wonders you can do by enforcing procedures (in terms of automation) and reports.
All the best.

In reply to Re: Supporting a production environment by rupesh
in thread Supporting a production environment by jeb6kids

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.