The best advice is the kind you don't want to hear. :-)

In this case it boils down to: "Don't host test and prod on the same server". Then you give the less-trusted devs access to the test server only. No live credentials will then be available to them.

This strategy has many other benefits. You can upgrade components (DB, webserver, O/S, perl, whatever) on the test platform in isolation, test to destruction and only then do the same on prod. Your test server does not need to have the same spec because it isn't handling the traffic and doesn't need to run 24x7 so you aren't looking at double the cost. Bite the bullet now - it will pay off in the long run.

🦛

In reply to Re: Holding site variables by hippo
in thread Holding site variables by Bod

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.