Yes, that is a modern additional feature to consider: Store configuration in a database (could even be user-specific!); you could reduce the .inifile to holding the database connection information.

But I wouldn't hard-code anything in the .pmwithout a very specific and strong argument to do so.

The benefits of keeping code and data separate is a very, very long list, and I've probably forgotten more reasons that some people will learn. Don't make your people edit .pmfiles just to make a config change. You are likely to live to regret it if you do.  :-)

Side note (and I really am just trying to be helpful, not demeaning in any way): A suit (sort of rhymes with "soot") is something you wear, or one of a family of cards in a deck of cards. I guess it can also be a legal action designed to seek compensation for perceived wrongs.

A suite (rhymes with "sweet") is a group of things tied together; a suite at a hotel is comprised of adjoining rooms, and a test suite is a bunch of tests that are grouped together as a (generally functional) block.