Last active
March 23, 2019 16:51
-
-
Save Masamasamasashito/c620015cc97240fbfd8af50b17d4f4cb to your computer and use it in GitHub Desktop.
Vagrantfile
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# -*- mode: ruby -*- | |
# vi: set ft=ruby : | |
# All Vagrant configuration is done below. The "2" in Vagrant.configure | |
# configures the configuration version (we support older styles for | |
# backwards compatibility). Please don't change it unless you know what | |
# you're doing. | |
Vagrant.configure("2") do |config| | |
# The most common configuration options are documented and commented below. | |
# For a complete reference, please see the online documentation at | |
# https://docs.vagrantup.com. | |
# Every Vagrant development environment requires a box. You can search for | |
# boxes at https://vagrantcloud.com/search. | |
config.vm.box = "yuya_tajima/kusanagi" | |
# Disable automatic box update checking. If you disable this, then | |
# boxes will only be checked for updates when the user runs | |
# `vagrant box outdated`. This is not recommended. | |
# config.vm.box_check_update = false | |
# Create a forwarded port mapping which allows access to a specific port | |
# within the machine from a port on the host machine. In the example below, | |
# accessing "localhost:8080" will access port 80 on the guest machine. | |
# NOTE: This will enable public access to the opened port | |
# config.vm.network "forwarded_port", guest: 80, host: 8080 | |
config.vm.network "forwarded_port", guest: 22, host: 12222, id: "ssh" | |
# Create a forwarded port mapping which allows access to a specific port | |
# within the machine from a port on the host machine and only allow access | |
# via 127.0.0.1 to disable public access | |
# config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1" | |
# 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" | |
# Share an additional folder to the guest VM. The first argument is | |
# the path on the host to the actual folder. The second argument is | |
# the path on the guest to mount the folder. And the optional third | |
# argument is a set of non-required options. | |
# config.vm.synced_folder "./kusanagi", "/home/kusanagi", owner: "kusanagi", group: "kusanagi", create: true , mount_options: ['dmode=755', 'fmode=644'] #shared folder | |
config.vm.synced_folder "./kusanagi", "/home/kusanagi", owner: "kusanagi", group: "kusanagi", create: true , mount_options: ['dmode=777', 'fmode=777'] #shared folder | |
# 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| | |
# # Display the VirtualBox GUI when booting the machine | |
# vb.gui = true | |
# | |
# # Customize the amount of memory on the VM: | |
vb.memory = "4096" #memory size | |
end | |
# | |
# View the documentation for the provider you are using for more | |
# information on available options. | |
# Enable provisioning with a shell script. Additional provisioners such as | |
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the | |
# documentation for more information about their specific syntax and use. | |
# config.vm.provision "shell", inline: <<-SHELL | |
# apt-get update | |
# apt-get install -y apache2 | |
# SHELL | |
end |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
synced_folderの利便性を考慮して、/home/kusanagi の中は全部 permission 777 です。ゲストOSをインターネットで外部公開しない様にご注意ください。
git bashだとディレクトリもファイルも緑色で違和感がヤバイです。
ホストOSでgit/sourcetreeを使ってVisualStudioCodeやAtomで開発、githubにプッシュを想定しています。
kusanagi provisionの後にドキュメントルートあたりでgit initしてください。
本番環境と開発環境でパーミッションまで同じ条件で検証することが出来れば理想的だと思いますが、そこまで出来ていません。
「owner: "kusanagi", group: "kusanagi", 」の部分はvagrantのほうがいい場合有り。
/home/kusanagiの中のディレクトリパーミッションを755、ファイルパーミッションを644としたい場合 48行目をコメントアウト、47行目を有効化してください。kusanagi provisionの後、GUIによるワードプレス初期設定で、wp-config.phpをコピペで作る必要が有ります。尚、vagrantでsynced_folderを使う場合の弱点は、共有フォルダの中ではVagrantfileから認識させてパーミッション変更しないといけないという点があります。ゲストOSでchmodやchownなどは出来ません。
ゲストOSのドキュメントルート内でシェルスクリプトを動かす場合、パーミッション777へVagrantfileを書き換えて、ホストOSから
vagrant reload
してください。その後、ゲストOSでsu - kusanagi
コマンドを行ってからシェルスクリプトを実行してください。メモリは4GBになっています。