Skip to content

Instantly share code, notes, and snippets.

@dpagini

dpagini/drupalvm-issues.md

Last active October 26, 2015 18:13
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dpagini/617e5cc98418354a258e to your computer and use it in GitHub Desktop.
Save dpagini/617e5cc98418354a258e to your computer and use it in GitHub Desktop.
Download ZIP
twitter reply to @geerlingguy
Raw
drupalvm-issues.md

@geerlingguy - thanks again for asking. I thought I could put more content into a Gist to explain my difficulties.

So, first of all, I wasted a LOT of time thinking that my share was not being mounted, when it actually was. The output of my vagrant up w/o NFS enabled on Windows shows me that my synced_folder is being mapped correctly on the guest OS. When I enable NFS, and run vagrant up again, I am missing this same line. However, if I vagrant ssh into the box, I can see that the folder was in fact mounted correctly... Unfortunately I didn't TRY that until hours into troubleshooting.

My next issue was actually getting winnfsd to work on my computer. I dont know if you have seen this before, but I realized that the only way to get the nfs shared folder to work was to specify SOME mount_options in Windows. It seems that the mount command was failing over and over again when that variable is empty. I'm not even EXACTLY sure what those options do for me, but I just realized that having no value here was failing over and over again for me. Should I maybe submit this as an issue? Have you seen this before, or are you aware of it? At the very least, both of these above notes might be helpful to add to the documentation for Windows?

I also have run into a few other small hurdles, and maybe these should be submitted as issues as well? Let me know.

  • If I install Drupal exclusively on the guest OS (then soft link to /vagrant folders for custom code), the whole site gets installed as root:root for the owner:group on the files. This means I have to go in after the vagrant up/provision and run sudo chown -R vagrant . and sudo chgrp -R www-data . to get the site to work properly. After going through your drupalvm repo, I noticed that you USED TO set these file permissions manually after the site creation, but that must have changed a little when you went to using a drush makefile? I also noticed that if I do install Drupal into a synced folder, that it correctly permissions the files... so it only appears to be when it installs Drupal to a guest-only location.

Last, more of just a simple question... is there an easy way to create softlinks in the drupal root during the provisioning? This is more of a feature request (unless it already exists?).

Really love this repo... thanks for all your time you put into this awesome tool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment