toresci.blogg.se

1. #DRUPAL VM SOLAR HOW TO#
2. #DRUPAL VM SOLAR INSTALL#
3. #DRUPAL VM SOLAR WINDOWS 7#
4. #DRUPAL VM SOLAR WINDOWS#

Change directories into Drupal VM: cd drupal-vmĬreate a shell script to create your project's directory and set it's permissions correctly:.Clone a copy of Drupal VM to your computer: git clone.When using Pageant this is not strictly required, but once this bug is resolved, you won't need Pageant at all, and you can just use start-ssh-agent.Run start-ssh-agent (so your SSH key is loaded and can be used in the VM).Note: In the rest of this guide, substitute projectname for your project's own machine name.

#DRUPAL VM SOLAR HOW TO#

See this guide for further instructions on how to have pageant.exe start on boot.Īt this point, we're ready to build a local development environment with Drupal VM. You should also ensure Pageant runs on system startup to ensure keys are always available when you need them.Right click on the Pageant item in the taskbar, and choose 'Add key', then navigate to where you saved id_rsa.ppk.Open pageant.exe (this opens a taskbar item).In the save dialog, save the file as id_rsa.ppk with type "PuTTY Private Key Files (*.ppk)".In the 'Actions' section, click "Save private key".Open puttygen.exe (inside C:\Program Files\PuTTY).Acquia Cloud under Profile > Credentials).ĭue to a bug in the current version of Vagrant, you need to use Pageant to allow Vagrant to use your SSH key inside the VM when running commands like vagrant up and vagrant provision.Īlso, Pageant requires a specially-formatted version of your key, so you'll need to use puttygen.exe to convert the key before loading it into Pageant. Also add the key into any other relevant service (e.g.Add the copied key into GitHub under Profile icon > Settings > SSH and GPG keys.

Copy the entire contents (from ssh-rsa to the end of your email address).Print the contents of the public key: cat C:\Users\\.ssh\id_rsa.pub.

#DRUPAL VM SOLAR INSTALL#

To make this work, you will need to install the following software:īefore doing any work with a project with code hosted on GitHub, Acquia Cloud, Redmine, or elsewhere, you need to create an SSH key pair so you can authenticate yourself to the main Git repository.

#DRUPAL VM SOLAR WINDOWS#

Here's how I used Drupal VM to run and develop an Acquia BLT-based project locally on Windows 7: Contents

#DRUPAL VM SOLAR WINDOWS 7#

Since a client I'm currently helping is stuck on Windows 7 for the short-term, and can't do internal development on a Mac or Linux (other OSes are not allowed on workstations), I decided to try to set up a project how I would set it up if I had to work in that situation.īasically, how do you get Drupal VM to perform as well (or better!) on a Windows 7 machine as it does on a Mac, while still allowing a native IDE (like PHPStorm or Notepad++) to be used?Īfter a couple days of tinkering, I've found the most stable solution, and that is to build Drupal VM 'outside in'-meaning you build your project inside Drupal VM, then share a folder from Drupal VM to Windows, currently using Samba (but in the future, SSHFS might be a viable option for Windows too!). but there were a lot of little inefficiencies in the recommended setup process that would lead to developers getting frustrated with the sluggish speed of the VM! Sure, I would make sure Drupal VM minimally ran inside Windows 10. I've often mentioned that Windows users who want to build modern Drupal sites and apps are going to have a bit of a difficult time, and even wrote a long post about why this is the case ( Developing with VirtualBox and Vagrant on Windows).īut for a long time, I haven't had much incentive to actually get my hands dirty with a Windows environment.