Contentbox 6 installation - password authentication failed (postgresql)

Hello!

I would like to add another entry regarding Contentbox 6 installation error, but this time with Postgresql database and upgraded contentbox-cli 1.6.0, Windows 10 and Commandbox 5.9.1.

Additionally i have also posted other similar problems with previous version of Contentbox-cli 1.5.2 and Commandbox 5.9.x to your #contentbox Slack Channel with Windows 10/8.1 and of course postgresql database.

I attach you several screenshots for your reference, unfortunately there is no log file and cfmigrations json file (similar to previous entry).

{
    "contentbox": {
        "manager": "cfmigrations.models.QBMigrationManager",
        "migrationsDirectory": "modules/contentbox/migrations/",
		"seedsDirectory": "tests/resources/seeds/",
        "properties": {
            "defaultGrammar": "AutoDiscover@qb",
			"schema" : "${DB_DATABASE}",
            "migrationsTable": "cfmigrations",
            "connectionInfo": {
				"connectionString": "${DB_CONNECTIONSTRING}",
                "class": "${DB_CLASS}",
                "username": "${DB_USER}",
                "password": "${DB_PASSWORD}",
                "bundleName": "${DB_BUNDLENAME}",
                "bundleVersion": "${DB_BUNDLEVERSION}"
            }
        }
    },
	"default": {
        "manager": "cfmigrations.models.QBMigrationManager",
        "migrationsDirectory": "resources/database/migrations/",
		"seedsDirectory": "resources/database/seeds/",
        "properties": {
            "defaultGrammar": "AutoDiscover@qb",
			"schema" : "${DB_DATABASE}",
            "migrationsTable": "cfmigrations_app",
            "connectionInfo": {
				"connectionString": "${DB_CONNECTIONSTRING}",
                "class": "${DB_CLASS}",
                "username": "${DB_USER}",
                "password": "${DB_PASSWORD}",
                "bundleName": "${DB_BUNDLENAME}",
                "bundleVersion": "${DB_BUNDLEVERSION}"
            }
        }
    }
}

Regards

Hi there,

I realise that your post is a little old now…
But - there is good news…

As a fellow PostgreSQL user, I too am having issues with installing ContentBox.
The issues have been identified and are being addressed.

The very short version of the issues is that PostgreSQL is stricter than all other DB brands.
Eg You cannot use a 0 or 1 as a boolean value in PostGres - so all DB related operations - need to ensure that true/false is used everywhere that a 0 or 1 is currently being used as Boolean value.

There is also a similar issue with Indexes having to be “quoted” strings for PostgreSQL - but other DB brands manage to work it out for themselves…

The Ortus guys are working on the changes needed to the underlying system - which takes a litlle while - as you can imagine - because any changes made to the internals to get PostgreSQL working properly/fully : need to be verified against the other supported DBs, too.

I have submitted a PR for the 0|1 → false|true changes required in the DB scripts that are used when initially installing ContentBox - so hopefully not too far away!

It’s not a great answer - but in the meantime - it does work flawlessly with MySQL/MariaDB - even if you temporarily use one of those for your local development…
ContentBox has a full export/import mechanism - so you can build up your CMS, today with MariaDB and once PostgreSQL support is finished, you can export from the MariaDB backed install and import into the PostgreSQL final destination.