Configuration files, typically in (or under) /etc or /usr/local/etc would be my choice. For packages installing in /opt/package, /opt/etc and /opt/package/etc are acceptable as well. For applications where it make sense, they could first look for a configuration file in the current directory, the users home directory, and /etc, using the first one they find. Or the other ways around, using all the find (with later ones overwriting previous values). Sophisticated apps could allow the use of environment variables and/or command line switches to overrule which configuration file to use.

I'd generally frown upon using configuration files that need to be retrieved over the network. Not only does that mean that if the service providing the configuration file isn't reachable, your applications cannot start (you're introducing a single point of failure), you'd still need a local configuration file anyway, because at least you need to configure where applications can find their configuration from.

A configuration file in a central location would be simple, but then anyone could read it, could see how to connect to the databases, etc.
That's what file permissions/ACLs are for.

In reply to Re: Where to store configuration information? by JavaFan
in thread Where to store configuration information? by Sue D. Nymme

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.