![]() ![]() 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. ![]() Press 'enter' three times to accept the defaults.Create an SSH key in the default location: ssh-keygen -t rsa -b 4096 -C " ".Open Cmder (right click and 'Run as Administrator').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. Configure a reverse-mounted shared folder. ![]() Here's how I used Drupal VM to run and develop an Acquia BLT-based project locally on Windows 7: Contents 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. maybe even allow switching to CentOS 6/7!).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. I might also need to add easier options for PHP version switching (like in acquia-cloud-vm) and add the ability to switch Ubuntu versions (should be simple enough to toggle 12.04 and 14.04 (current default). I really think that, short of using an actual playbook that builds your prod server (or entire infrastructure) locally, this VM is now capable of doing most of what's necessary for reliable local Drupal development. ![]() Site that uses a Drush make file (configure vagrant_synced_folders and set build_from_makefile to true).Site that uses multisite for multiple domains pointing to the same docroot (configure vagrant_synced_folders, add multiple apache_vhosts with the same documentroot, and set build_from_makefile to false).Site with docroot shared from host machine (configure vagrant_synced_folders and apache_vhosts, and set build_from_makefile to false).I'd like to document how to do some of the most common setups: Now that #33 has made the drupal-vm a lot more flexible (no longer does it always install a site from a makefile, you can use different kinds of Drupal sites (like sites where the entire site is in a local directory on the host, and the user installs a database), and as many as you want at the same time. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |