Vagrantfile. Конфиг файл по русски

Для настройки виртуальной машины и окружения используется файл конфига  Vagrantfile. Этот файл нужно располагать в корне разрабатываемого проекта, т.к. обычно его нужно держать в GITе, чтобы другие (особенно новые) участники проекта смогли без танцев развернуть проект локально. Ниже информация по основным параметрам файла конфигурации Vagrant адаптирована для русскоговорящей публики.

Структура

Базовая структура файла конфигурации Vagrantfile выглядит примерно так:

# -*- mode: ruby -*-
# vi: set ft=ruby :

# Версия синтаксиса (не меняйте)
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # ... все опции конфигурации находятся здесь ...
end

Параметры

Назначение базовых опций конфигурации:

# Название бокса, на основе которого запускается виртуальная машина
config.vm.box = "precise32"

# Перенаправление локальных портов на порты виртуальной машины
# localhost:8080 на нашей машине будет смотреть на 80 порт виртуалки
config.vm.network :forwarded_port, host: 8080, guest: 80

# Каталоги для синхронизации (синхронизация 2-х сторонняя!)
# По умолчанию каталог проекта синхронизируется с каталогом /vagrant
# на виртуалке. И некоторое предустановленное ПО уже настроено
# на использование этой дирректории (Apache)
config.vm.synced_folder "/home/user/www/project", "/var/www"
                            локальный каталог      виртуалка

# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
# config.vm.box_url = "http://domain.com/path/to/above.box"

# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network :private_network, ip: "192.168.33.10"

# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network :public_network

# If true, then any SSH connections made will enable agent forwarding.
# Default value: false
# config.ssh.forward_agent = true

# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider :virtualbox do |vb|
#   # Don't boot with headless mode
#   vb.gui = true
#
#   # Use VBoxManage to customize the VM. For example to change memory:
#   vb.customize ["modifyvm", :id, "--memory", "1024"]
# end
#
# View the documentation for the provider you're using for more
# information on available options.

# Enable provisioning with Puppet stand alone.  Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file demo.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# #   ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# #   content => "Welcome to your Vagrant-built virtual machine!
# #               Managed by Puppet.\n"
# # }
#
# config.vm.provision :puppet do |puppet|
#   puppet.manifests_path = "manifests"
#   puppet.manifest_file  = "site.pp"
# end

# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision :chef_solo do |chef|
#   chef.cookbooks_path = "../my-recipes/cookbooks"
#   chef.roles_path = "../my-recipes/roles"
#   chef.data_bags_path = "../my-recipes/data_bags"
#   chef.add_recipe "mysql"
#   chef.add_role "web"
#
#   # You may also specify custom JSON attributes:
#   chef.json = { :mysql_password => "foo" }
# end

# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision :chef_client do |chef|
#   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
#   chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
#   chef.validation_client_name = "ORGNAME-validator"

#vagrant, #виртулизация