From be952a9d084449a565ee6b8eec81d3e9b55468eb Mon Sep 17 00:00:00 2001 From: Joe McLaughlin <joemcl@users.noreply.github.com> Date: Thu, 3 Oct 2019 00:17:15 -0700 Subject: [PATCH] updating drush link updating drush link from drush dot ws (apparently an online casino website in... Indonesia?) to drush dot org --- docs/tools/civibuild.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tools/civibuild.md b/docs/tools/civibuild.md index 6a02f566..21bd07a5 100644 --- a/docs/tools/civibuild.md +++ b/docs/tools/civibuild.md @@ -11,7 +11,7 @@ Creating a full development environment for CiviCRM requires a lot of work, e.g. The *civibuild* command automates this process. It includes different build-types that are useful for core development, such as *drupal-clean* (a barebones Drupal+Civi site) and *wp-demo* (a WordPress+Civi site with some example content). -Note: There are a number of build tools on the market which can, e.g., create a Drupal web site (like [drush](http://drush.ws/)) or WordPress web site (like [wp-cli](http://wp-cli.org/)). Civibuild does not aim to replace these. Unfortunately, such tools generally require extra work for a Civi developer environment. Civibuild works with these tools and and fills in missing parts. +Note: There are a number of build tools on the market which can, e.g., create a Drupal web site (like [drush](http://drush.org/)) or WordPress web site (like [wp-cli](http://wp-cli.org/)). Civibuild does not aim to replace these. Unfortunately, such tools generally require extra work for a Civi developer environment. Civibuild works with these tools and and fills in missing parts. ## Build types -- GitLab