Make sure that you select the plugins root folder (where your main plugin file is) when you’re adding the “Host Source”. Scroll to the bottom and add your plugin folder. Open the Volumes tab and you’ll see a list of directories that are being symlinked. Once you download the plugin, upload it into Local to install it and you’ll see a new “More” tab that contains a “Volumes” link under the site name. So the plugin was created to handle all the linking for you. The older version of Local runs all of it’s containers inside of a virtual machine which makes the symlink process complicated. If you are using Local Lightning, skip this section-it only applies to the older version. If you are not using Local Lightning (Flywheels latest version of Local), you’ll need to download this plugin so you can map directories to your site’s container. We can use these to keep our plugin code separate from our WordPress install.

It doesn’t care about the location of the original folder because your computer is automatically redirecting it. When you symlink a directory into Local’s install, it just sees the contents of the linked folder. When you create an alias (sometimes seen as “shortcut”), any time you click on it to open, your computer just redirects you to the source and opens the folder or program you created the alias from. What Are Symlinks?Ī symlink is basically just a redirection-it’s the exact same thing as a folder or program alias. Since Local by Flywheel uses containers for each site, you can symlink, or symbolically link, a directory into your install. Using symlinks with Local by Flywheel helps keep the plugin code isolated so it’s easier to manage. When developing plugins with Local by Flywheel it’s a good idea to keep the plugin code separate from your WordPress installs.

Local by flywheel wordpress version