Debugging w/ PhpStorm

[Clinton Gallagher]

Said no one on their death bed "I'll always remember the good times I had trying to configure @PhpStorm to use #Xdebug to debug @WordPress running on VVV/Vagrant @Ubuntu boxes installed on @VirtualBox VMs on #Windows10"

I'm doing okay with Vagrant per se but debugging with PhpStorm is not going well at all. I really need help with this. PhpStorm just does not want me to learn to configure a remote server. Help!

[Alvaro Miranda Aguilera]

screenshots of the errors?

can you share vagrant file?

On Thu, Jan 25, 2018 at 7:08 PM, Clinton Gallagher <clinton.s...@gmail.com> wrote:

Said no one on their death bed "I'll always remember the good times I had trying to configure @PhpStorm to use #Xdebug to debug @WordPress running on VVV/Vagrant @Ubuntu boxes installed on @VirtualBox VMs on #Windows10"

I'm doing okay with Vagrant per se but debugging with PhpStorm is not going well at all. I really need help with this. PhpStorm just does not want me to learn to configure a remote server. Help!

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/11a5da78-0840-4113-bf25-07987ff29b5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Clinton Gallagher]

I'll send this weekend...<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link"
target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1"></a></div>

On Thu, Jan 25, 2018 at 3:54 PM, Alvaro Miranda Aguilera
<kik...@gmail.com> wrote:
> screenshots of the errors?
>
> can you share vagrant file?
>
>
> On Thu, Jan 25, 2018 at 7:08 PM, Clinton Gallagher
> <clinton.s...@gmail.com> wrote:
>>
>> Said no one on their death bed "I'll always remember the good times I had
>> trying to configure @PhpStorm to use #Xdebug to debug @WordPress running on
>> VVV/Vagrant @Ubuntu boxes installed on @VirtualBox VMs on #Windows10"
>>
>> I'm doing okay with Vagrant per se but debugging with PhpStorm is not
>> going well at all. I really need help with this. PhpStorm just does not want
>> me to learn to configure a remote server. Help!
>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
>> of those guidelines may result in your removal from this mailing list.
>>
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> 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 vagrant-up+...@googlegroups.com.

>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vagrant-up/11a5da78-0840-4113-bf25-07987ff29b5d%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Alvaro
>

> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---

> You received this message because you are subscribed to a topic in the
> Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vagrant-up/SrW6RSKMZdE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vagrant-up+...@googlegroups.com.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewzzUUiHdW0jXJxVPt%2BgUDJ7hqqFx68KV7CBf8Vk1SZMA%40mail.gmail.com.

> For more options, visit https://groups.google.com/d/optout.



--

Clinton Gallagher
tapABILITIES, LLC
Wauwatosa, Milwaukee County, USA
TEL 414-774-2557 Central
CEL 414-243-8211
WWW tapabilities.com
@tapABILITIES

[Clinton Gallagher]

I can send some things up this weekend. According to phpinfo
everything is setup and configured on the Ubuntu box. I've upgraded
to Vagrant 2.0 and have to do some messing around with VVV which
remains behind the update. What will we be looking for in the vagrant
file?

On Thu, Jan 25, 2018 at 3:54 PM, Alvaro Miranda Aguilera
<kik...@gmail.com> wrote:

> screenshots of the errors?
>
> can you share vagrant file?
>
>
> On Thu, Jan 25, 2018 at 7:08 PM, Clinton Gallagher
> <clinton.s...@gmail.com> wrote:
>>
>> Said no one on their death bed "I'll always remember the good times I had
>> trying to configure @PhpStorm to use #Xdebug to debug @WordPress running on
>> VVV/Vagrant @Ubuntu boxes installed on @VirtualBox VMs on #Windows10"
>>
>> I'm doing okay with Vagrant per se but debugging with PhpStorm is not
>> going well at all. I really need help with this. PhpStorm just does not want
>> me to learn to configure a remote server. Help!
>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
>> of those guidelines may result in your removal from this mailing list.
>>
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> 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 vagrant-up+...@googlegroups.com.

>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vagrant-up/11a5da78-0840-4113-bf25-07987ff29b5d%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Alvaro
>

> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---

> You received this message because you are subscribed to a topic in the
> Google Groups "Vagrant" group.

> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vagrant-up/SrW6RSKMZdE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vagrant-up+...@googlegroups.com.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewzzUUiHdW0jXJxVPt%2BgUDJ7hqqFx68KV7CBf8Vk1SZMA%40mail.gmail.com.

> For more options, visit https://groups.google.com/d/optout.



--

[Clinton Gallagher]

### VAGRANT FILE
###
###
###
# -*- mode: ruby -*-
# vi: set ft=ruby ts=2 sw=2 et:

require 'yaml'

vagrant_dir = File.expand_path(File.dirname(__FILE__))

if ! ENV['VVV_SKIP_LOGO'] then
branch = `if [ -f #{vagrant_dir}/.git/HEAD ]; then git rev-parse
--abbrev-ref HEAD; else echo 'novcs'; fi`
puts " \033[38;5;196m__ _\033[38;5;118m__ _\033[38;5;33m__
__ \033[38;5;129m ____ "
puts " \033[38;5;196m\\ \\ / \033[38;5;118m\\ \\ /
\033[38;5;33m\\ \\ / / \033[38;5;129m|___ \\ "
puts " \033[38;5;196m \\ \\ / /\033[38;5;118m \\ \\ /
/\033[38;5;33m \\ \\ / / \033[38;5;129m __) | "
puts " \033[38;5;196m \\ V / \033[38;5;118m \\ V / \033[38;5;33m
\\ V / \033[38;5;129m / __/ "
puts " \033[38;5;196m \\_/ \033[38;5;118m \\_/ \033[38;5;33m
\\_/ \033[38;5;129m|_____| "
puts ""
puts " \033[38;5;196mVarying \033[38;5;118mVagrant
\033[38;5;33mVagrants \033[38;5;129mv2.1.0-" + branch
puts " \033[0mDocs: https://varyingvagrantvagrants.org/"
puts " \033[0mContribute: https://github.com/varying-vagrant-vagrants/vvv"
puts " \033[0mDashboard: http://vvv.test"
puts "\033[0m"
end



if File.file?(File.join(vagrant_dir, 'vvv-custom.yml')) then
vvv_config_file = File.join(vagrant_dir, 'vvv-custom.yml')
else
vvv_config_file = File.join(vagrant_dir, 'vvv-config.yml')
end

vvv_config = YAML.load_file(vvv_config_file)

if ! vvv_config['sites'].kind_of? Hash then
vvv_config['sites'] = Hash.new
end

if ! vvv_config['hosts'].kind_of? Hash then
vvv_config['hosts'] = Array.new
end

vvv_config['hosts'] += ['vvv.dev']
vvv_config['hosts'] += ['vvv.test']
vvv_config['hosts'] += ['vvv.local']
vvv_config['hosts'] += ['vvv.localhost']

vvv_config['sites'].each do |site, args|
if args.kind_of? String then
repo = args
args = Hash.new
args['repo'] = repo
end

if ! args.kind_of? Hash then
args = Hash.new
end

defaults = Hash.new
defaults['repo'] = false
defaults['vm_dir'] = "/srv/www/#{site}"
defaults['local_dir'] = File.join(vagrant_dir, 'www', site)
defaults['branch'] = 'master'
defaults['skip_provisioning'] = false
defaults['allow_customfile'] = false
defaults['nginx_upstream'] = 'php'
defaults['hosts'] = Array.new

vvv_config['sites'][site] = defaults.merge(args)

site_host_paths = Dir.glob(Array.new(4) {|i|
vvv_config['sites'][site]['local_dir'] + '/*'*(i+1) + '/vvv-hosts'})

vvv_config['sites'][site]['hosts'] += site_host_paths.map do |path|
lines = File.readlines(path).map(&:chomp)
lines.grep(/\A[^#]/)
end.flatten

vvv_config['hosts'] += vvv_config['sites'][site]['hosts']
vvv_config['sites'][site].delete('hosts')
end

if ! vvv_config['utility-sources'].kind_of? Hash then
vvv_config['utility-sources'] = Hash.new
end
vvv_config['utility-sources']['core'] =
'https://github.com/Varying-Vagrant-Vagrants/vvv-utilities.git'

if ! vvv_config['utilities'].kind_of? Hash then
vvv_config['utilities'] = Hash.new
end

if ! vvv_config['vm_config'].kind_of? Hash then
vvv_config['vm_config'] = Hash.new
end

defaults = Hash.new
defaults['memory'] = 1024
defaults['cores'] = 1

vvv_config['vm_config'] = defaults.merge(vvv_config['vm_config'])

vvv_config['hosts'] = vvv_config['hosts'].uniq

Vagrant.configure("2") do |config|

# Store the current version of Vagrant for use in conditionals when dealing
# with possible backward compatible issues.
vagrant_version = Vagrant::VERSION.sub(/^v/, '')

# Configurations from 1.0.x can be placed in Vagrant 1.1.x specs
like the following.
config.vm.provider :virtualbox do |v|
v.customize ["modifyvm", :id, "--memory", vvv_config['vm_config']['memory']]
v.customize ["modifyvm", :id, "--cpus", vvv_config['vm_config']['cores']]
v.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
v.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
v.customize ["modifyvm", :id, "--rtcuseutc", "on"]
v.customize ["modifyvm", :id, "--audio", "none"]
v.customize ["modifyvm", :id, "--paravirtprovider", "kvm"]

# Set the box name in VirtualBox to match the working directory.
vvv_pwd = Dir.pwd
v.name = File.basename(vagrant_dir) + "_" +
(Digest::SHA256.hexdigest vagrant_dir)[0..10]
end

# Configuration options for the Parallels provider.
config.vm.provider :parallels do |v|
v.update_guest_tools = true
v.customize ["set", :id, "--longer-battery-life", "off"]
v.memory = vvv_config['vm_config']['memory']
v.cpus = vvv_config['vm_config']['cores']
end

# Configuration options for the VMware Fusion provider.
config.vm.provider :vmware_fusion do |v|
v.vmx["memsize"] = vvv_config['vm_config']['memory']
v.vmx["numvcpus"] = vvv_config['vm_config']['cores']
end

# Configuration options for Hyper-V provider.
config.vm.provider :hyperv do |v, override|
v.memory = vvv_config['vm_config']['memory']
v.cpus = vvv_config['vm_config']['cores']
end

# SSH Agent Forwarding
#
# Enable agent forwarding on vagrant ssh commands. This allows you
to use ssh keys
# on your host machine inside the guest. See the manual for `ssh-add`.
config.ssh.forward_agent = true

# Default Ubuntu Box
#
# This box is provided by Ubuntu vagrantcloud.com and is a nicely
sized (332MB)
# box containing the Ubuntu 14.04 Trusty 64 bit release. Once this
box is downloaded
# to your host computer, it is cached for future use under the
specified box name.
config.vm.box = "ubuntu/trusty64"

# The Parallels Provider uses a different naming scheme.
config.vm.provider :parallels do |v, override|
override.vm.box = "parallels/ubuntu-14.04"
end

# The VMware Fusion Provider uses a different naming scheme.
config.vm.provider :vmware_fusion do |v, override|
override.vm.box = "netsensia/ubuntu-trusty64"
end

# VMWare Workstation can use the same package as Fusion
config.vm.provider :vmware_workstation do |v, override|
override.vm.box = "netsensia/ubuntu-trusty64"
end

# Hyper-V uses a different base box.
config.vm.provider :hyperv do |v, override|
override.vm.box = "ericmann/trusty64"
end

config.vm.hostname = "vvv"

# Local Machine Hosts
#
# If the Vagrant plugin hostsupdater
(https://github.com/cogitatio/vagrant-hostsupdater) is
# installed, the following will automatically configure your local
machine's hosts file to
# be aware of the domains specified below. Watch the provisioning
script as you may need to
# enter a password for Vagrant to access your hosts file.
#
# By default, we'll include the domains set up by VVV through the
vvv-hosts file
# located in the www/ directory and in vvv-config.yml.
if defined?(VagrantPlugins::HostsUpdater)

# Pass the found host names to the hostsupdater plugin so it can
perform magic.
config.hostsupdater.aliases = vvv_config['hosts']
config.hostsupdater.remove_on_suspend = true
end

# Private Network (default)
#
# A private network is created by default. This is the IP address
through which your
# host machine will communicate to the guest. In this default
configuration, the virtual
# machine will have an IP address of 192.168.50.4 and a virtual
network adapter will be
# created on your host machine with the IP of 192.168.50.1 as a gateway.
#
# Access to the guest machine is only available to your local host.
To provide access to
# other devices, a public network should be configured or port
forwarding enabled.
#
# Note: If your existing network is using the 192.168.50.x subnet,
this default IP address
# should be changed. If more than one VM is running through
VirtualBox, including other
# Vagrant machines, different subnets should be used for each.
#
config.vm.network :private_network, id: "vvv_primary", ip: "192.168.50.4"

config.vm.provider :hyperv do |v, override|
override.vm.network :private_network, id: "vvv_primary", ip: nil
end

# Public Network (disabled)
#
# Using a public network rather than the default private network
configuration will allow
# access to the guest machine from other devices on the network. By
default, enabling this
# line will cause the guest machine to use DHCP to determine its IP
address. You will also
# be prompted to choose a network interface to bridge with during
`vagrant up`.
#
# Please see VVV and Vagrant documentation for additional details.
#
# config.vm.network :public_network

# Port Forwarding (disabled)
#
# This network configuration works alongside any other network
configuration in Vagrantfile
# and forwards any requests to port 8080 on the local host machine
to port 80 in the guest.
#
# Port forwarding is a first step to allowing access to outside
networks, though additional
# configuration will likely be necessary on our host machine or
router so that outside
# requests will be forwarded from 80 -> 8080 -> 80.
#
# Please see VVV and Vagrant documentation for additional details.
#
# config.vm.network "forwarded_port", guest: 80, host: 8080

# Drive mapping
#
# The following config.vm.synced_folder settings will map
directories in your Vagrant
# virtual machine to directories on your local machine. Once these
are mapped, any
# changes made to the files in these directories will affect both
the local and virtual
# machine versions. Think of it as two different ways to access the
same file. When the
# virtual machine is destroyed with `vagrant destroy`, your files
will remain in your local
# environment.

# /srv/database/
#
# If a database directory exists in the same directory as your Vagrantfile,
# a mapped directory inside the VM will be created that contains these files.
# This directory is used to maintain default database scripts as
well as backed
# up MariaDB/MySQL dumps (SQL files) that are to be imported
automatically on vagrant up
config.vm.synced_folder "database/", "/srv/database"

# If the mysql_upgrade_info file from a previous persistent database
mapping is detected,
# we'll continue to map that directory as /var/lib/mysql inside the
virtual machine. Once
# this file is changed or removed, this mapping will no longer
occur. A db_backup command
# is now available inside the virtual machine to backup all
databases for future use. This
# command is automatically issued on halt, suspend, and destroy if
the vagrant-triggers
# plugin is installed.
if File.exists?(File.join(vagrant_dir,'database/data/mysql_upgrade_info'))
then
if vagrant_version >= "1.3.0"
config.vm.synced_folder "database/data/", "/var/lib/mysql",
:mount_options => [ "dmode=777", "fmode=777" ]
else
config.vm.synced_folder "database/data/", "/var/lib/mysql",
:extra => 'dmode=777,fmode=777'
end

# The Parallels Provider does not understand "dmode"/"fmode" in
the "mount_options" as
# those are specific to Virtualbox. The folder is therefore
overridden with one that
# uses corresponding Parallels mount options.
config.vm.provider :parallels do |v, override|
override.vm.synced_folder "database/data/", "/var/lib/mysql",
:mount_options => []
end
end

# /srv/config/
#
# If a server-conf directory exists in the same directory as your Vagrantfile,
# a mapped directory inside the VM will be created that contains these files.
# This directory is currently used to maintain various config files
for php and
# nginx as well as any pre-existing database files.
config.vm.synced_folder "config/", "/srv/config"

# /srv/log/
#
# If a log directory exists in the same directory as your
Vagrantfile, a mapped
# directory inside the VM will be created for some generated log files.
config.vm.synced_folder "log/", "/srv/log", :owner => "www-data"

# /srv/www/
#
# If a www directory exists in the same directory as your
Vagrantfile, a mapped directory
# inside the VM will be created that acts as the default location
for nginx sites. Put all
# of your project files here that you want to access through the web server
if vagrant_version >= "1.3.0"
config.vm.synced_folder "www/", "/srv/www/", :owner => "www-data",
:mount_options => [ "dmode=775", "fmode=774" ]
else
config.vm.synced_folder "www/", "/srv/www/", :owner => "www-data",
:extra => 'dmode=775,fmode=774'
end

vvv_config['sites'].each do |site, args|
if args['local_dir'] != File.join(vagrant_dir, 'www', site) then
if vagrant_version >= "1.3.0"
config.vm.synced_folder args['local_dir'], args['vm_dir'],
:owner => "www-data", :mount_options => [ "dmode=775", "fmode=774" ]
else
config.vm.synced_folder args['local_dir'], args['vm_dir'],
:owner => "www-data", :extra => 'dmode=775,fmode=774'
end
end
end

config.vm.provision "fix-no-tty", type: "shell" do |s|
s.privileged = false
s.inline = "sudo sed -i '/tty/!s/mesg n/tty -s \\&\\& mesg n/'
/root/.profile"
end

# The Parallels Provider does not understand "dmode"/"fmode" in the
"mount_options" as
# those are specific to Virtualbox. The folder is therefore
overridden with one that
# uses corresponding Parallels mount options.
config.vm.provider :parallels do |v, override|
override.vm.synced_folder "www/", "/srv/www/", :owner =>
"www-data", :mount_options => []

vvv_config['sites'].each do |site, args|
if args['local_dir'] != File.join(vagrant_dir, 'www', site) then
override.vm.synced_folder args['local_dir'], args['vm_dir'],
:owner => "www-data", :mount_options => []
end
end
end

# The Hyper-V Provider does not understand "dmode"/"fmode" in the
"mount_options" as
# those are specific to Virtualbox. Furthermore, the normal shared
folders need to be
# replaced with SMB shares. Here we switch all the shared folders to
us SMB and then
# override the www folder with options that make it Hyper-V compatible.
config.vm.provider :hyperv do |v, override|
override.vm.synced_folder "www/", "/srv/www/", :owner =>
"www-data", :mount_options =>
["dir_mode=0775","file_mode=0774","forceuid","noperm","nobrl","mfsymlinks"]
vvv_config['sites'].each do |site, args|
if args['local_dir'] != File.join(vagrant_dir, 'www', site) then
override.vm.synced_folder args['local_dir'], args['vm_dir'],
:owner => "www-data", :mount_options =>
["dir_mode=0775","file_mode=0774","forceuid","noperm","nobrl","mfsymlinks"]
end
end
# Change all the folder to use SMB instead of Virtual Box shares
override.vm.synced_folders.each do |id, options|
if ! options[:type]
options[:type] = "smb"
end
end
end

# Customfile - POSSIBLY UNSTABLE
#
# Use this to insert your own (and possibly rewrite) Vagrant config
lines. Helpful
# for mapping additional drives. If a file 'Customfile' exists in
the same directory
# as this Vagrantfile, it will be evaluated as ruby inline as it loads.
#
# Note that if you find yourself using a Customfile for anything
crazy or specifying
# different provisioning, then you may want to consider a new
Vagrantfile entirely.
if File.exists?(File.join(vagrant_dir,'Customfile')) then
eval(IO.read(File.join(vagrant_dir,'Customfile')), binding)
end

vvv_config['sites'].each do |site, args|
if args['allow_customfile'] then
paths = Dir[File.join(args['local_dir'], '**', 'Customfile')]
paths.each do |file|
eval(IO.read(file), binding)
end
end
end

# Provisioning
#
# Process one or more provisioning scripts depending on the
existence of custom files.
#
# provison-pre.sh acts as a pre-hook to our default provisioning
script. Anything that
# should run before the shell commands laid out in provision.sh (or
your provision-custom.sh
# file) should go in this script. If it does not exist, no extra
provisioning will run.
if File.exists?(File.join(vagrant_dir,'provision','provision-pre.sh')) then
config.vm.provision "pre", type: "shell", path: File.join(
"provision", "provision-pre.sh" )
end

# provision.sh or provision-custom.sh
#
# By default, Vagrantfile is set to use the provision.sh bash script
located in the
# provision directory. If it is detected that a provision-custom.sh
script has been
# created, that is run as a replacement. This is an opportunity to
replace the entirety
# of the provisioning provided by default.
if File.exists?(File.join(vagrant_dir,'provision','provision-custom.sh')) then
config.vm.provision "custom", type: "shell", path: File.join(
"provision", "provision-custom.sh" )
else
config.vm.provision "default", type: "shell", path: File.join(
"provision", "provision.sh" )
end

vvv_config['utility-sources'].each do |name, repo|
config.vm.provision "utility-source-#{name}",
type: "shell",
path: File.join( "provision", "provision-utility-source.sh" ),
args: [
name,
repo
]
end

vvv_config['utilities'].each do |name, utilities|

if ! utilities.kind_of? Array then
utilities = Hash.new
end
utilities.each do |utility|
config.vm.provision "utility-#{name}-#{utility}",
type: "shell",
path: File.join( "provision", "provision-utility.sh" ),
args: [
name,
utility
]
end
end

vvv_config['sites'].each do |site, args|
config.vm.provision "site-#{site}",
type: "shell",
path: File.join( "provision", "provision-site.sh" ),
args: [
site,
args['repo'].to_s,
args['branch'],
args['vm_dir'],
args['skip_provisioning'].to_s,
args['nginx_upstream']
]
end


# provision-post.sh acts as a post-hook to the default provisioning.
Anything that should
# run after the shell commands laid out in provision.sh or
provision-custom.sh should be
# put into this file. This provides a good opportunity to install
additional packages
# without having to replace the entire default provisioning script.
if File.exists?(File.join(vagrant_dir,'provision','provision-post.sh')) then
config.vm.provision "post", type: "shell", path: File.join(
"provision", "provision-post.sh" )
end

# Always start MariaDB/MySQL on boot, even when not running the full
provisioner
# (run: "always" support added in 1.6.0)
if vagrant_version >= "1.6.0"
config.vm.provision :shell, inline: "sudo service mysql restart",
run: "always"
config.vm.provision :shell, inline: "sudo service nginx restart",
run: "always"
end

# Vagrant Triggers
#
# If the vagrant-triggers plugin is installed, we can run various
scripts on Vagrant
# state changes like `vagrant up`, `vagrant halt`, `vagrant
suspend`, and `vagrant destroy`
#
# These scripts are run on the host machine, so we use `vagrant ssh`
to tunnel back
# into the VM and execute things. By default, each of these scripts
calls db_backup
# to create backups of all current databases. This can be overridden
with custom
# scripting. See the individual files in config/homebin/ for details.
if defined? VagrantPlugins::Triggers
config.trigger.after :up, :stdout => true do
system({'VVV_SKIP_LOGO'=> 'true'}, "vagrant ssh -c 'vagrant_up'")
end
config.trigger.before :reload, :stdout => true do
system({'VVV_SKIP_LOGO'=> 'true'}, "vagrant ssh -c 'vagrant_halt'")
end
config.trigger.after :reload, :stdout => true do
system({'VVV_SKIP_LOGO'=> 'true'}, "vagrant ssh -c 'vagrant_up'")
end
config.trigger.before :halt, :stdout => true do
system({'VVV_SKIP_LOGO'=> 'true'}, "vagrant ssh -c 'vagrant_halt'")
end
config.trigger.before :suspend, :stdout => true do
system({'VVV_SKIP_LOGO'=> 'true'}, "vagrant ssh -c 'vagrant_suspend'")
end
config.trigger.before :destroy, :stdout => true do
system({'VVV_SKIP_LOGO'=> 'true'}, "vagrant ssh -c 'vagrant_destroy'")
end
end
end

On Fri, Jan 26, 2018 at 9:02 PM, Clinton Gallagher

[Alvaro Miranda Aguilera]

how are you connecting?

the project have a private network, try with  192.168.50.4 

[Clinton Gallagher]

Don't understand what you are suggesting Alvaro. Where and what do you
suggest I edit to use 192.168.50.4

> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vagrant-up/SrW6RSKMZdE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vagrant-up+...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyetnORLhU%2BXJnMJb6Jspj6g1ySYqEBdzvcfTCtKhGn9A%40mail.gmail.com.

[Alvaro Miranda Aguilera]

the project you are using sets in the guest

from your host computer try to open a browser to  192.168.50.4

try to use phpstorm to  192.168.50.4

On Mon, Jan 29, 2018 at 4:52 PM, Clinton Gallagher <clinton.s...@gmail.com> wrote:

Don't understand what you are suggesting Alvaro. Where and what do you
suggest I edit to use 192.168.50.4

On Sat, Jan 27, 2018 at 2:40 AM, Alvaro Miranda Aguilera
<kik...@gmail.com> wrote:
> how are you connecting?
>
> the project have a private network, try with  192.168.50.4
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vagrant-up/SrW6RSKMZdE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to

> vagrant-up+unsubscribe@googlegroups.com.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyetnORLhU%2BXJnMJb6Jspj6g1ySYqEBdzvcfTCtKhGn9A%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.

--
Clinton Gallagher
tapABILITIES, LLC
Wauwatosa, Milwaukee County, USA
TEL   414-774-2557 Central
CEL   414-243-8211
WWW tapabilities.com
@tapABILITIES

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---

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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAH%3Ddq197G1fYUoEigbkUWEbMLp5Y2cYBjskW06QFWa-MiWAfnQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro