I propose to use phinx to handle database installation instead of a SQL script; in order to handle schema changes.
Created database is exactly the same than the old script one (checked using a pg_dump and compare results); with the exception of phinx metadata table.
In order to set up phinx on an existing database, first run ./vendor/bin/sphinx status. This will create the metadata table; and tell you the current status is "down". Once done, run the following query:
I propose to use phinx to handle database installation instead of a SQL script; in order to handle schema changes.
Created database is exactly the same than the old script one (checked using a pg_dump and compare results); with the exception of phinx metadata table.
In order to set up phinx on an existing database, first run
./vendor/bin/sphinx status
. This will create the metadata table; and tell you the current status is "down". Once done, run the following query:A new run of phinx status, and see it's "up" :)
An
INSTALL.md
file is provided for fresh installs.