Update execution of drush to direct calls by ddev, rather than exec-style
This commit is contained in:
parent
0ea5c5273d
commit
8918395020
1 changed files with 6 additions and 6 deletions
|
@ -112,17 +112,17 @@ $conf['allow_authorize_operations'] = FALSE;
|
|||
Once you also have a working Drush installation and a live instance, you can then aquire and export the initial configuration with:
|
||||
|
||||
```
|
||||
ddev . drush sql-sync @live @self
|
||||
ddev . drush -y cex
|
||||
ddev drush sql-sync @live @self
|
||||
ddev drush -y cex
|
||||
```
|
||||
|
||||
Similarly, you can get live data and files down to your local development environment any time with:
|
||||
|
||||
```
|
||||
ddev . drush -y sql-dump > data/paranoia.sql
|
||||
ddev . drush -y sql-drop
|
||||
ddev . drush -y sql-sync @live @self
|
||||
ddev . drush -y rsync @live:%files @self:%files
|
||||
ddev drush -y sql-dump > data/paranoia.sql
|
||||
ddev drush -y sql-drop
|
||||
ddev drush -y sql-sync @live @self
|
||||
ddev drush -y rsync @live:%files @self:%files
|
||||
```
|
||||
|
||||
And get the latest code for your distribution (here presuming [build_source](https://gitlab.com/drutopia-platform/build_source/)) like this:
|
||||
|
|
Loading…
Reference in a new issue