Deploy to Heroku button, broken.

[DougHayward]

I have just tried running the 'Deploy to Heroku' feature, located within the Readme of this repo. I made no changes to the setting automatically provided, however I got the following error during the 'Run scripts & Scale Dynos' section:

�[37;41m ! [CAUTION] This operation should not be executed in a production environment! 
 Creating database schema...
[2018-01-24 00:08:32] console.ERROR: Error thrown while running command "{command}". Message: "{message}" {"error":"[object] (Doctrine\\DBAL\\Exception\\DriverException(code: 0): An exception occurred in driver: SQLSTATE[22023]: Invalid parameter value: 7 ERROR:  invalid value for parameter \"client_encoding\": \"utf8mb4\" at /app/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractPostgreSQLDriver.php:95, Doctrine\\DBAL\\Driver\\PDOException(code: 22023): SQLSTATE[22023]: Invalid parameter value: 7 ERROR:  invalid value for parameter \"client_encoding\": \"utf8mb4\" at /app/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:106, PDOException(code: 22023): SQLSTATE[22023]: Invalid parameter value: 7 ERROR:  invalid value for parameter \"client_encoding\": \"utf8mb4\" at /app/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:104)","command":"doctrine:schema:create","message":"An exception occurred in driver: SQLSTATE[22023]: Invalid parameter value: 7 ERROR:  invalid value for parameter \"client_encoding\": \"utf8mb4\""} []
�[33mIn AbstractPostgreSQLDriver.php line 95:
�[37;41m  An exception occurred in driver: SQLSTATE[22023]: Invalid parameter value:
�[37;41m  7 ERROR:  invalid value for parameter "client_encoding": "utf8mb4" 
�[33mIn PDOConnection.php line 106:
�[37;41m  SQLSTATE[22023]: Invalid parameter value: 7 ERROR:  invalid value for param
�[37;41m  eter "client_encoding": "utf8mb4"
�[33mIn PDOConnection.php line 104:
�[37;41m  SQLSTATE[22023]: Invalid parameter value: 7 ERROR:  invalid value for param
�[37;41m  eter "client_encoding": "utf8mb4"
�[32mdoctrine:schema:create [--dump-sql] [--em [EM]] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] �[39m�[32m<command>

[stof]

Well, the config is not optimized for postgresql anymore, but for sqlite and mysql. So deploying it directly to heroku without any change might indeed fail when using postgresql.

[javiereguiluz]

Can't Heroku run some commands or make some changes in some config file or script to prepare the app for their platform? Otherwise, we might remove the button because a failing feature hurts both Symfony's and Heroku's reputation.

[bocharsky-bw]

Or we can tweak configs on our side to support both PostgreSQL and SQLite

[javiereguiluz]

Maybe we have discussed before ... but is it really impossible to run SQLite on Heroku servers? It looks like the best solution.

[bocharsky-bw]

They provide add-ons, but I don't see any SQLite ones there :/
https://elements.heroku.com/addons

And I suppose they don't have SQLite installed on the main PHP-FPM image

UPD: Here's the proof: https://devcenter.heroku.com/articles/sqlite3

[stof]

sqlite does not work, as the filesystem is ephemeral (so even with a single dyno, you would still loose your DB every day)