![]() Unlike DrupalVM (which is added via composer as a project dependency) Lando, Docksal, and DDev all get downloaded and installed on your machine. ![]() I have, on more than one occasion, installed a version of Docker Desktop that Lando doesn’t like. So, I would strongly urge you to review what version of Lando you plan on installing and then confirming what version of Docker Desktop it supports. ![]() I’ve found that Lando is a bit more opinionated about Docker Desktop version than Docksal and DDev (and I use it a bit more frequently). Those are: vagrant plugin install vagrant-vbguest Installing Docker Desktop for Lando, DOcksal, and DDev There are a few other recommended plugins recommended for DrupalVM. Installing Vagrant, Ansible, and Virtual Box for DrupalVMįor DrupalVM you’ll want all of these! brew cask install vagrant brew install ansibleįor VirtualBox, I would confirm which version is currently supported by DrupalVM via the docs and download directly from the VirtualBox page. Lando, Docksal, and DDev likely need sudo to install and get the requirements setup, but don’t usually need it for daily operation (so they may be better options for you if you don’t have persistent administrative privileges on our host machine). It requires sudo every time you start / stop the VM. Protip: If you can’t get sudo access to your machine, DrupalVM definitely won’t be an option for you. This is a common blocker for some organizations that prevent some folks from running local development environments as their company’s security policies prohibit their developers from having admin access. Once you wade into the these next installation sections, you will begin needing sudo / administrative access to your local. Obviously your miles may vary here depending on what solution you use for containerization / virtualization. At this stage, I installed both the necessary dependencies for Vagrant (so I could run Drupal VM) and Docker Desktop (so I could run Lando and DDev). The next big round of installation really surrounds the type of development you’re doing. You can do so by following my guide in this post. I highly recommend upping the memory limit (mine started at 128MB on a brand new machine) to at least 2GB (2048MB). Once completed, you’ll see something like this:Ī common composer problem is that composer is beholden to the PHP memory limit on your machine. While Homebrew isn’t stricting speaking required, the rest of this guide will assume you’re using it AND it drastically simplifies what is to come. You can install Homebrew with the following command: /bin/bash -c "$(curl -fsSL )" Basically, Homebrew is a dependency manager for your OS and it makes it a ton easier to install development packages and/or change versions of bundled packages that come with your OS (e.g. I don’t use it “daily” but when I need it, it’s a lifesaver. Homebrew is one of my favorite development tools. This is my go to source for command reminders and help! Install Homebrew ![]() Protip: Github has incredible documentation on SSH keys and security. if I still have my old computer in my possession I’ll hold off on removing the old key, but I’ll still create a new one. Github, your web hosting,, etc.) and uploading the SSH key. Once generated, I start logging into the services I’ll need access to (e.g. If you use different email addresses on different sites, you may need a different SSH key for each. You can do this via your terminal using the following command: $ ssh-keygen -t rsa -b 4096 -C email address in this example should be the one you have used for your account on such services as Github, Gitlab, etc. ![]() The first “real” thing I always do on a new machine is generate a new SSH key. Setting Up for Development Generating a new SSH Key ![]()
0 Comments
Leave a Reply. |