From 9b9f147d81a6a2351a4c0fb62acb733506285386 Mon Sep 17 00:00:00 2001
From: Joe McLaughlin <joemcl@users.noreply.github.com>
Date: Sat, 7 Sep 2019 01:28:20 -0700
Subject: [PATCH] Update docs/tools/buildkit.md
Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>
---
docs/tools/buildkit.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/tools/buildkit.md b/docs/tools/buildkit.md
index a7a1cb08..4d07abb2 100644
--- a/docs/tools/buildkit.md
+++ b/docs/tools/buildkit.md
@@ -19,7 +19,7 @@ curl -Ls https://civicrm.org/get-buildkit.sh | bash -s -- --full --dir ~/buildki
!!! note
- * When executing the above command, you should *not* run as `root`, as it *will* cause failures. However, you *should* have `sudo` permissions. You shouldn't run the curl buildkit command as sudo. It will sudo itself for the bits that need it.
+ * When executing the above curl/install command, you should *not* run it as `root` - including via `sudo`, as doing so *will* cause failures. However, you *should* have `sudo` permissions as the script includes several `sudo` statements where these are required.
* The `--full` option is *very opinionated*; it specifically installs `php`, `apache`, and `mysql` (rather than `hhvm`, `nginx`, `lighttpd`, or `percona`). If you try to mix `--full` with alternative systems, then expect conflicts.
* If you use the Ubuntu feature for "encrypted home directories", then don't put buildkit in `~/buildkit`. Consider `/opt/buildkit`, `/srv/buildkit`, or some other location that remains available during reboot.
--
GitLab