Ha, beautiful! That appears to be working perfectly. I didn't realize you could use synced_folder on a sub-folders of an already synced folder, and it never crossed my mind to try it.
...always the simple things /facepalm. Thanks -Nathan On Friday, April 29, 2016 at 9:38:59 PM UTC-6, Alvaro Miranda Aguilera wrote: > > Hello, > What happen if you add just more lines? > > config.vm.synced_folder ".", "/vagrant", :mount_options => [ "dmode=755", > "fmode=744" ] > config.vm.synced_folder "public", "/vagrant/public", :mount_options => [ > "dmode=755","fmode=644" ] > > ? > > On Sat, Apr 30, 2016 at 9:37 AM, Nathan Crews <[email protected] > <javascript:>> wrote: > >> I've been using Vagrant for a while but just now found the Mailing list! >> so I thought i'd ask a permissions question that has been eating at me ( >> scanned the list but didn't see this, but apologies if i missed it ) >> >> I'm running Vagrant on Windows 10 and Virtualbox to launch a ubuntu VM >> for development. >> >> I have a folder structure like this >> >> - Dev/ >> ---- /public/ >> ---- /ops/ >> ---- Vagrantfile >> >> Where "public" is set as the doc root of apache, and "ops" has some shell >> scripts i use. >> >> I need the file permissions of public to be 755/644 directories/files >> and the shell scripts need to be executable. >> >> I'm currently sidesteping this by setting all the files to 744 >> config.vm.synced_folder ".", "/vagrant", :mount_options => [ "dmode=755", >> "fmode=744" ] >> >> But if possible i'd like to have /vagrant/public ( could be everything in >> /vagrant except /ops ) to 755/644 >> and still let all the files in /vagrant/ops be set to executable. >> >> >> Does anyone have a solution to this or better plan to include executable >> scripts into their dev environments? >> >> Thanks >> Nathan >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/0cca29f5-9f2b-46bf-a5c9-754ce3eed029%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/0cca29f5-9f2b-46bf-a5c9-754ce3eed029%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0a7c462b-8ead-4ebf-8c49-5773da731a6c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
