hello, your english is pretty good, so no issues at all. (this came from someone that speak spanish)
you have 2 options, as I see it. 1. Mount a folder with the permissions you need. http://docs.vagrantup.com/v2/synced-folders/basic_usage.html example: config.vm.synced_folder "src/", "/srv/website", owner: "apache", group: "apache" 2. you can copy the files/folder to the destination you require. There is a soon to be documented feature, that you can read here: https://github.com/mitchellh/vagrant/pull/3022/files that allow you to provision a folder or file Alvaro On Thu, Feb 27, 2014 at 10:15 AM, Marc Richter < [email protected]> wrote: > Hi everyone, > > there are shared folders in VirtualBox and vagrant uses it, per default, > in mounting /vagrant to the working folder. As far as I understood the > vagrant concept, this folder shall be used to work with your development > files on your host and interact with it inside vagrant. For example: When > developing web applications, you usually configure the webserver inside the > vagrant box to use something in your working folder as its document root > and edit those files using your native IDE. You then look at the results by > reloading the webpage, served by the vagrant box's httpd server. > > If you work with complex applications like Drupal or TYPO3, these > applications need to create files and folders in that directories, such as > caching files and directories. But when running the vagrant box on a Linux > host, this seems to be tricky: The webserver seems to have no access to > folders, it creates itself, because the usual Linux FS-Permissions and > ownerships do not apply. Let me show you an example using TYPO3: > > Let's assume, you started your vagrant box with the VirtualBox provider > and configured apache httpd to serve files from /vagrant/site1 . TYPO3 > tries to create a cache folder in /vagrant/site1/typo3temp then. If you > issue commands like "chown" or "chmod" in the vagrant box on this folder, > it won't change anything. If you do this on the host, you can set 777 > permissions recursively onto the working folder, which is also shown in the > box. But when the apache user then creates a subfolder in that directory > (which succeeds), this folder again is not owned by the apache user, and > has default umask permission. In result, apache again cannot write to these > newly created files and directories. > > On Windows hosts, this seems to not be of importance, since all > directories and files within the working Dir have 777 permission, anyways. > > I hope I described the issue properly. Please do not be mad on me because > of my bad english; I'm not a native speaker .. > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
