質問編集履歴

1

vagrant fileの中身の記載

2020/04/29 02:10

投稿

uuuuuu
uuuuuu

スコア13

test CHANGED
File without changes
test CHANGED
@@ -59,3 +59,153 @@
59
59
  どうすればいいか調べてみたのですが、3日ほど行き詰まった状態なので質問させていただきました。
60
60
 
61
61
  どなたか回答お願いします。
62
+
63
+
64
+
65
+ **vagrantfileの中身**(おそらく何も変わっていないはずです)
66
+
67
+ ```
68
+
69
+ -*- mode: ruby -*-
70
+
71
+ # vi: set ft=ruby :
72
+
73
+
74
+
75
+ # All Vagrant configuration is done below. The "2" in Vagrant.configure
76
+
77
+ # configures the configuration version (we support older styles for
78
+
79
+ # backwards compatibility). Please don't change it unless you know what
80
+
81
+ # you're doing.
82
+
83
+ Vagrant.configure("2") do |config|
84
+
85
+ # The most common configuration options are documented and commented below.
86
+
87
+ # For a complete reference, please see the online documentation at
88
+
89
+ # https://docs.vagrantup.com.
90
+
91
+
92
+
93
+ # Every Vagrant development environment requires a box. You can search for
94
+
95
+ # boxes at https://vagrantcloud.com/search.
96
+
97
+ config.vm.box = "ubuntu/bionic64"
98
+
99
+
100
+
101
+ # Disable automatic box update checking. If you disable this, then
102
+
103
+ # boxes will only be checked for updates when the user runs
104
+
105
+ # `vagrant box outdated`. This is not recommended.
106
+
107
+ # config.vm.box_check_update = false
108
+
109
+
110
+
111
+ # Create a forwarded port mapping which allows access to a specific port
112
+
113
+ # within the machine from a port on the host machine. In the example below,
114
+
115
+ # accessing "localhost:8080" will access port 80 on the guest machine.
116
+
117
+ # NOTE: This will enable public access to the opened port
118
+
119
+ # config.vm.network "forwarded_port", guest: 80, host: 8080
120
+
121
+
122
+
123
+ # Create a forwarded port mapping which allows access to a specific port
124
+
125
+ # within the machine from a port on the host machine and only allow access
126
+
127
+ # via 127.0.0.1 to disable public access
128
+
129
+ # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"
130
+
131
+
132
+
133
+ # Create a private network, which allows host-only access to the machine
134
+
135
+ # using a specific IP.
136
+
137
+ # config.vm.network "private_network", ip: "192.168.33.10"
138
+
139
+
140
+
141
+ # Create a public network, which generally matched to bridged network.
142
+
143
+ # Bridged networks make the machine appear as another physical device on
144
+
145
+ # your network.
146
+
147
+ # config.vm.network "public_network"
148
+
149
+
150
+
151
+ # Share an additional folder to the guest VM. The first argument is
152
+
153
+ # the path on the host to the actual folder. The second argument is
154
+
155
+ # the path on the guest to mount the folder. And the optional third
156
+
157
+ # argument is a set of non-required options.
158
+
159
+ # config.vm.synced_folder "../data", "/vagrant_data"
160
+
161
+
162
+
163
+ # Provider-specific configuration so you can fine-tune various
164
+
165
+ # backing providers for Vagrant. These expose provider-specific options.
166
+
167
+ # Example for VirtualBox:
168
+
169
+ #
170
+
171
+ # config.vm.provider "virtualbox" do |vb|
172
+
173
+ # # Display the VirtualBox GUI when booting the machine
174
+
175
+ # vb.gui = true
176
+
177
+ #
178
+
179
+ # # Customize the amount of memory on the VM:
180
+
181
+ # vb.memory = "1024"
182
+
183
+ # end
184
+
185
+ #
186
+
187
+ # View the documentation for the provider you are using for more
188
+
189
+ # information on available options.
190
+
191
+
192
+
193
+ # Enable provisioning with a shell script. Additional provisioners such as
194
+
195
+ # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
196
+
197
+ # documentation for more information about their specific syntax and use.
198
+
199
+ # config.vm.provision "shell", inline: <<-SHELL
200
+
201
+ # apt-get update
202
+
203
+ # apt-get install -y apache2
204
+
205
+ # SHELL
206
+
207
+ end
208
+
209
+
210
+
211
+ ```