Skip to content
Snippets Groups Projects
Unverified Commit 2afd3520 authored by Joe McLaughlin's avatar Joe McLaughlin Committed by GitHub
Browse files

clarification on running curl as sudo

Added to line 22 - "You shouldn't run the curl buildkit command as sudo. It will sudo itself for the bits that need it."
parent 915d9aa8
No related branches found
No related tags found
No related merge requests found
......@@ -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.
* 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.
* 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.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment