vagrant

Vagrant + Xdebug + Atom

▼魔方 西西 提交于 2019-12-31 07:11:05
问题 I have a vagrant box with xdebug installed, running on OSX, but Im struggling to get the Atom xdebug plugin ( php-debug ) to connect to it. I pasted the phpinfo(); data into the xdebug validation site and it said all was good. And you can see all the xdebug settings. I have mapped port 9000 in the vagrant file. config.vm.network :forwarded_port, guest: 9000, host: 9000 The vagrant box has host only network that exposes 192.168.10.100 as the IP of the server. And I've tried all manner of

Bash variable character replacement ends up to an empty string or a command not valid

£可爱£侵袭症+ 提交于 2019-12-31 05:52:05
问题 I am working on a shell script to retrieve variable content from a JSON file via JQ. The JSON file is in string format (no matter whether this is a real string or a number) and to retrieve the variable in my bash script I did something like this my_domain=$(cat /vagrant/data_bags/config.json | jq ."app"[0]."domain") The above code once echoed results in "mydomain" with a beginning and a trailing quote sign. I though this was a normal behaviour of the echo command. However, while concatenating

Vagrant port forwarding not working. Cups not accesible from host

拈花ヽ惹草 提交于 2019-12-31 01:49:06
问题 So I'm working with vagrant and I'm trying to use it as a printing server. I installed cups. Internally everything works just fine. I can even make a quick curl to my localhost:631 (cups port inside my vagrant) and there's everything. The thing is I cant access it in any way I try from the host machine. Obviously I forwarded the port and I've tried with several ports. I've also tried with Debian squeeze and Ubuntu 12.04. Here is my current Vagrantfile Vagrant.configure("2") do |config| config

Pass command line argument to vagrant shell script provisioner

拈花ヽ惹草 提交于 2019-12-31 01:42:11
问题 Similar to this question: Passing variable to a shell script provisioner in vagrant I want to pass variables to a shell script provisioner but I want to set these variables on the command line when I call the provisioner. Is this possible? 回答1: This is what I would try - I guess there are possibilities as Vagrantfile is a ruby script, you can use most of ruby possibilities Be careful though as vagrant might need to check for variables, for example when doing vagrant up arg1 arg2 , it expects

Pass command line argument to vagrant shell script provisioner

依然范特西╮ 提交于 2019-12-31 01:41:08
问题 Similar to this question: Passing variable to a shell script provisioner in vagrant I want to pass variables to a shell script provisioner but I want to set these variables on the command line when I call the provisioner. Is this possible? 回答1: This is what I would try - I guess there are possibilities as Vagrantfile is a ruby script, you can use most of ruby possibilities Be careful though as vagrant might need to check for variables, for example when doing vagrant up arg1 arg2 , it expects

Bundle install is using a different Ruby version?

北慕城南 提交于 2019-12-30 20:12:46
问题 I tried to install Ruby 2.0.0-p353 on Vagrant using knife-solo. When I logged in as root and vagrant, ruby -v returns Ruby 2.0.0-p353. However, when I run bundle install in a Rails project, the following statement is displayed: Your Ruby version is 1.8.7, but your Gemfile specified 2.0.0 The default version of Ruby is 1.8.7, so I think bundle install is referring to this. What should I do to solve this problem? $ cat site-cookbooks/ruby/recipes/default.rb group 'rbenv' do action :create

Bundle install is using a different Ruby version?

半世苍凉 提交于 2019-12-30 20:11:35
问题 I tried to install Ruby 2.0.0-p353 on Vagrant using knife-solo. When I logged in as root and vagrant, ruby -v returns Ruby 2.0.0-p353. However, when I run bundle install in a Rails project, the following statement is displayed: Your Ruby version is 1.8.7, but your Gemfile specified 2.0.0 The default version of Ruby is 1.8.7, so I think bundle install is referring to this. What should I do to solve this problem? $ cat site-cookbooks/ruby/recipes/default.rb group 'rbenv' do action :create

How do I Sequel Pro with PuPHPet?

大城市里の小女人 提交于 2019-12-30 11:41:09
问题 I have just set up a virtual machine using Vagrant and Puphpet. I know I have MySQL because I can mysql in the command line. I just did a basic install. I don't know how to set up my sequel pro to get access though. I am using the "Standard" option on the Sequel Pro application (the others are "Socket" and "SSH"). Is that the right one to use? The values I enter are; Name: awesome Host: 192.168.56.101 Username: mlovely Password: mlovely Port: 9000 Here is my part of my config.yaml file that

How do I Sequel Pro with PuPHPet?

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-30 11:40:11
问题 I have just set up a virtual machine using Vagrant and Puphpet. I know I have MySQL because I can mysql in the command line. I just did a basic install. I don't know how to set up my sequel pro to get access though. I am using the "Standard" option on the Sequel Pro application (the others are "Socket" and "SSH"). Is that the right one to use? The values I enter are; Name: awesome Host: 192.168.56.101 Username: mlovely Password: mlovely Port: 9000 Here is my part of my config.yaml file that

How to debug “Vagrant cannot forward the specified ports on this VM” message

百般思念 提交于 2019-12-29 19:03:23
问题 I'm trying to start a Vagrant instance and getting the following message: Vagrant cannot forward the specified ports on this VM, since they would collide with another VirtualBox virtual machine's forwarded ports! The forwarded port to 4567 is already in use on the host machine. To fix this, modify your current projects Vagrantfile to use another port. Example, where '1234' would be replaced by a unique host port: config.vm.forward_port 80, 1234 I opened VirtualBox, but I don't have any