Recommendations for development database accounts?

Question

What are the best credential processing methods for internal development databases? For both applications and developers?

We are currently creating a separate user / password for each development database, and we transfer these credentials to our code repository. But we want to get away from storing credentials in our repositories. The problem is that both our developers and applications need access to databases.

• Is it good to provide developers with their own personal account that gives them access to all the developer databases? Perhaps even all databases of developers and production?
• Should developers use their personal account in their development environment? Or should they use another?
• If they must use a different account, should each developer database have a separate set of credentials? Or should we create one account that can access all the developer databases that developers can use in all their applications?
• If we need to use separate accounts for each dev database, how should developers get these credentials when they set up a new development environment for themselves? We found that trying to manually track them (e.g. wikis) is very error prone and quickly becoming obsolete.

If that matters, we use MySQL (Percona, to be precise).

Answer 1

, , , 100% . MySQL . . Percona , , .

, , .

, . , , / .

, . :

    # cat config.php
    <?php

    $mysql_user="@@MYSQL_USER@";
    $mysql_password="@@MYSQL_PASSWORD@";
    $mysql_host="@@MYSQL_HOST@";
    $mysql_db="@@MYSQL_DB@";

    ?> 

, , , .spec

    %files www
    %config(noreplace) %attr(640, root, apache)  %{_sysconfdir}/%{project_name}/config.php