We provide config/config.ini.sample.php, which implies that a user could copy and configure this manually as config.ini.php.
SQLSTATE  Access denied for user "%s"
(followed by a backtrace)
SQLSTATE  Unknown database "%s"
Critical Error during the update process:
Database piwik is empty. You must edit or remove your Piwik configuration file.
sounds good - also, a simple solution could be to explain in a comment in config.sample that this is not meant to be copied, users should go through the installation process first etc.
I vote for a comment in config.sample.ini to explain that this is not meant to be copied with a link to the installation guide (piwik.org/docs/installation/)
In , refs #991 - add comment to config.ini.sample.php to not copy this file
Have a look into the repository of EXT:piwikintegration for TYPO3.
Here is the direct link to the helper class with the function makePiwikConfigured:
This class is used to fetch, extract and install piwik fully automated. It supports updating existing databases. It's forced to use a hardcoded prefix, to make it compatible with TYPO3.
The tracking code is developed in a standalone extension:
Best regards Kay
I've added a reference to comment:7 to #161.
(In ) fixes #991 - redirect to Installation 'welcome' (displaying alternate text & error message) if database connection fails