Start using migrations #5
Reference in New Issue
Block a user
Delete Branch "start-using-migrations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
New : use migration instead of changing sql dump
Task : add first name, last name and mail(email) to the order
Smoke test :
open Co-Market and select first item on the left (or some other that is working ; example url : http://localhost:8000/co-market/14/302), add it to the cart. Go to the cart and complete ordering process. When finished, check in database that order contains required user details following this steps :
in terminal, run :
sudo docker exec -it legacywiaas_db_1 /bin/bash
now, open mysql : mysql -u root -p (password is root)
execute in mysql : use ricoh_dash
and after that : SELECT billingFirstName, billingLastName, billingMail from orders;
all data should be empty except in one row, that is order made by you
added 1 commit
bea9ba5e- restore URL-s to live serverCompare with previous version
changed the description
Why do you repeat the values of environment variables, like DB name , user and pass if we are using the same credentials.
This is ok only if you are planning to add diffenet DB user to phinx
I left PROD and TEST variables in case we need different databases, but they are obsolete, should I remove those ?
This can be written better.
You don't need to repeat keys like host , name etc... What if we had more environments ??
Just determine the environment first , load values for that environment into variables
and add variable values to those keys
merged
mentioned in commit
92f237c82f