therefore it fails to see that VirtualBox is installed in Windows since it's only able to see executables in the Ubuntu virtual environment.).
#Drupal vm update#
When you get to the blt vm step, run that command, but expect it to fail with a red error message (as of Windows 10 Anniversary Update the WSL can't easily call out to Windows executables from the Ubuntu Bash environment.
If it looks like it's not really doing anything, try pressing a key (like down arrow) the Ubuntu Bash environment can get temporarily locked up if you accidentally scroll down.Note that the composer create-project command could take a while (5-10 minutes usually, but could be slower).Run the commands inside the BLT - creating a new project guide.Set up your Git username and password following these BLT directions.
#Drupal vm install#
Install PHP and Composer (no need for Node.js at this time) following these BLT Windows install directions.You should also install the following: vagrant plugin install vagrant-vbguest and vagrant plugin install vagrant-hostsupdater.Install the Windows Subsystem for Linux with Ubuntu Bash.I created a video/screencast of the entire process (just to prove to myself it was reliably able to be rebuilt), which I've embedded below, and I'll also post the detailed step-by-step instructions (with extra notes and cautionary asides) below. On most projects I'm involved with, at least one or two developers will have a Linux or macOS environment, and that person would be the one to set up BLT.īut if you need to set up BLT and Drupal VM entirely within Windows, there are a few things you need to do unique to the Windows environment, due to the fact that Windows handles CLIs, line endings, and symlinks differently than other OSes. One group of developers had a requirement that everyone only use Windows 10 to do everything. There's a reason I ask everyone to submit issues to the GitHub tracker and not to my email!
Chances are 20 other people have run into the exact problem before. If you're getting errors with any step along the way, copy out parts of the error message that seem relevant and search Google and/or the Drupal VM issue queue.Just be careful to protect the private key from prying eyes. copy it from your Mac to PC, inside a VM, wherever). And you can take one public/private key pair and put it anywhere (e.g. id_rsa.pub) can be shared freely and should be added to your GitHub, Acquia, etc. If you need to use SSH keys for anything, remember that the private key ( id_rsa) is secret.These two plugins make a lot of little issues go away. When using Vagrant, run vagrant plugin install vagrant-vbguest and vagrant plugin install vagrant-hostsupdater.It's basically an Ubuntu 14.04 CLI running inside Windows. Some things don't work here yet (like calling Windows binaries from WSL), but hopefully a lot will be improved by the next Windows 10 update (slated for Q2 2017). If at all possible, run as much as possible in the Windows Subsystem for Linux with Ubuntu Bash.Just for starters, I'll give a few tips for success when using Drupal VM (or most any Linux-centric dev tooling or programming languages) on Windows 10:
#Drupal vm how to#
Quite often, I get inquiries from developers about how to get Drupal VM working on Windows 10-and this is often after encountering error after error due to many different factors.
0 kommentar(er)
