From 89183950207980df599a2f56c9f22a29e0d97751 Mon Sep 17 00:00:00 2001 From: Chris Thompson Date: Wed, 7 Jul 2021 18:20:40 -0400 Subject: [PATCH] Update execution of drush to direct calls by ddev, rather than exec-style --- tools/creating-new-drutopia-site.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/tools/creating-new-drutopia-site.md b/tools/creating-new-drutopia-site.md index 08ae06f..fa171fb 100644 --- a/tools/creating-new-drutopia-site.md +++ b/tools/creating-new-drutopia-site.md @@ -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: