Update README to move re-load legacy db step

Oops...the dropped db must be re-created by deploy first!
This commit is contained in:
Chris Thompson 2019-07-30 16:49:56 -04:00
parent 92ef3b8fe7
commit ff14f4284a

View file

@ -73,13 +73,13 @@ ddev . drush mim --group="migrate_drupal_7_geo"
1. Extract the uploaded files (still on server):
- Unzip the uploaded database file (this expects there to be only ONE such file): `gunzip *.mysql.gz`
- Rename the database file: `mv *.mysql geo_legacy.sql`
- Read the db source into the proper database: `mysql geo_legacy < geo_legacy.sql`
- Unpack the files, but first cd to where they go (again, there should only be ONE file ending in .tar.gz in home): `cd site/d7/sites/default/files/` and untar: `tar xzf ~/*.tar.gz` (this will take a minute/two).
- The server side is ready! Log off by typing `ctrl+d`
1. Now perform a deployment with drutopia_hosting. This will install the site using the minimal profile and existing config:
- `ahoy deploy-build news`
- `ahoy deploy-site geo_live`
1. Return to the server (`ssh geo_live@drutopia.org`) and run the migration:
1. Return to the server (`ssh geo_live@drutopia.org`), load legacy db and run the migration:
- Read the db source into the proper database: `mysql geo_legacy < geo_legacy.sql`
- `drush mim --group="migrate_drupal_7_geo"`
## Post go-live tasks