14

I have been using http://www.puphpet.com successfully to generate vagrant+puppet environments for a number of projects. Then this week I got tasked with writing a prototype for a project using Laravel 4. Since I'm not going to be the one working on the project full time, I figured it would be best to make a VM environment for it that the next person can just clone for the repo. Not having much experience with Laravel 4 I got everything to run in the dev environment just fine. Then I tried to run the first migration and here the problems start with the app/storage file permissions.

1. app/storage must be writable by the web user

Fine, took out id: vagrant from the synced folder provisioning and set the owner & group to www-data like so:

 config.vm.synced_folder "./www", "/var/www", owner: "www-data", group: "www-data"

2. Artisan can only be run from inside the vagrant box to have access to the DB

Fine, vagrant ssh and run artisan from the www folder.

3. app/storage & app/database have to be writable by the vagrant user in order to use migrations

Grrr, ok, added the following awful piece of code to the vagrant file (note, tried to do this in Puppet first and it didn't take):

config.vm.provision :shell, :inline =>
  "usermod -a -G www-data vagrant"

4. app/storage & app/database are not writeable by the group

Argh!!! Ok, let's try this Puppet directive:

file { "/var/www/app/storage":
  source => "/var/www/app/storage/",
  mode => 0775,
  ensure  => 'directory',
  owner   => 'www-data',
  group   => 'www-data',
  recurse => true
}

Nope, doesn't work. Tried to do the same with the Puppet exec {} directive to no effect. It seems that permissions for the vagrant synced folder are set by the host machine, not the guest.

Finally ended up manually changing the permissions for the folder in the host machine. Is there any simpler way to do this? I would really just like to be able to give the next dev a worry free environment they can clone from the repo, not have them re-setup everything after cloning.

UPDATE

We've figured out that if we change the Apache run user, vagrant doesn't override it on reload. So we've done that manually and it's working better than changing the synced folder's permissions & owner. Now we're just trying to figure out how to make that change manually in Puppet.

4

3 回答 3

19

在 Twitter 上进行了一些讨论后，得出以下结论：

VirtualBox 对 vagrant 有一个限制，不允许您从来宾操作系统内部为同步文件夹设置权限。在 github 上看到这个问题。

您可以使用以下代码从 vagrant 文件中设置同步文件夹权限：

config.vm.synced_folder ".", "/vagrant", :mount_options => ["dmode=777","fmode=666"]

或者，您可以将 Apache 运行时用户从 puppet 清单中更改为 vagrant，如下所示：

exec { "change_httpd_user":
    command => "sed -i 's/www-data/vagrant/g' /etc/apache2/envvars",
    onlyif => "/bin/grep -q 'www-data' '/etc/apache2/envvars'",
    notify => Service['apache2'],
    require => Package['apache2'],
}

file { "/var/lock/apache2":
    ensure => "directory",
    owner => "vagrant",
    group => "vagrant",
    require => Exec['change_httpd_user'],
}

或以上任意组合

于 2013-09-29T12:38:47.317 回答
9

我没有在我的设置中使用 pupphet，我想出了 2 个解决方案：

(1) 在我的 bootstrap.sh 文件中：

sudo sed -i 's/APACHE_RUN_USER=.*/APACHE_RUN_USER=vagrant/g' /etc/apache2/envvars
sudo sed -i 's/APACHE_RUN_GROUP=.*/APACHE_RUN_GROUP=www-data/g' /etc/apache2/envvars

(2) 我是我的 VagrantFile：

config.vm.synced_folder "./", "/vagrant", id: "vagrant-root" , :owner => "vagrant", :group => "www-data"

config.vm.synced_folder "./app/storage", "/vagrant/app/storage", id: "vagrant-storage",
    :owner => "vagrant",
    :group => "www-data",
    :mount_options => ["dmode=775","fmode=664"]

config.vm.synced_folder "./public", "/vagrant/public", id: "vagrant-public",
    :owner => "vagrant",
    :group => "www-data",
    :mount_options => ["dmode=775","fmode=664"]
于 2013-11-15T17:39:32.160 回答
0

查看 Vagrant 文档的这一部分http://docs.vagrantup.com/v2/synced-folders/basic_usage.html

于 2013-12-13T15:22:26.093 回答