db-migrate needs to pull database configuration from somewhere. Right now it uses the database.json but it is easier if we use the DATABASE_URL environment variable that db-migrate supports. Otherwise we'd have to add entries to database.json for all the different environments. Unfortunately db-migrate doesn't respect DATABASE_URL if database.json exists so it has been removed. See here for workaround used in deployments.
Updated documentation so migration command uses DATABASE_URL
Removed database creation command from documentation as it is handled by origin-box
First pull request? Read our guide to contributing
Checklist:
Description:
db-migrateneeds to pull database configuration from somewhere. Right now it uses thedatabase.jsonbut it is easier if we use theDATABASE_URLenvironment variable thatdb-migratesupports. Otherwise we'd have to add entries todatabase.jsonfor all the different environments. Unfortunatelydb-migratedoesn't respectDATABASE_URLifdatabase.jsonexists so it has been removed. See here for workaround used in deployments.DATABASE_URLorigin-box