Switch docker-compose.yml to use pgsql

[djdefi]

Change to docker-compose.yml to utilize postgresql instead of MySQL. Does not require immediately updating docs, since MySQL will still work fine also.

Closes #2

[djdefi]

ping @cachethq/docker

[n0mer]

@rtrauntvein so what exactly do you want

and why do you change to pgsql

[djdefi]

Just looking for review of the PR.

This is based on suggestion of using Postgres instead of MySQL by @GrahamCampbell or @jbrooksuk

[GrahamCampbell]

and why do you change to pgsql

Because it's way better than mysql. ;P

[n0mer]

it is less popular , according to http://db-engines.com/en/ranking

[GrahamCampbell]

it is less popular

Doesn't mean it's not better.

[jbrooksuk]

In our experience - with StyleCI - MySQL has a lot of quirks that we can avoid.

[n0mer]

i would quote Donald E. Knuth here, "premature optimization is root of all evil".

If your users demand this - fine. If it solves some problem that already exists in Cachet - also fine.

If this to show off your personal taste - you're on your own :)

[n0mer]

@rtrauntvein as for PR itself - why did you change data-only container to the folder on host machine?

[djdefi]

There was no data volume or data only container for persistence of the Database before.

Sent from my iPhone

On Aug 28, 2015, at 2:39 AM, Nikolay Gorylenko notifications@github.com wrote:

@rtrauntvein as for PR itself - why did you change data-only container to the folder on host machine?

—
Reply to this email directly or view it on GitHub.

[n0mer]

@rtrauntvein you are right, no volumes for compose. You just hardcoded the path on host machine, that this "compose" script will demand.

[djdefi]

The directory would get created automatically, but I will just take it out.

[GrahamCampbell]

Any news on this?