Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Michael Akopov
@makopov
Has anyone tried these recipes with centos?
Sergey Storchay
@r8
It uses custom apt repositories in few places, so it will not work with centos without modifications
Michael Akopov
@makopov
Is this the right place to discuss errors that came up during provisioning?
Jjemastr
@Jjemastr

Hi, guys. Sorry if now will be very stupid question, but after “vagrant up” my ubuntu32 on vmware says:”No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
vagrant up --provider=PROVIDER, which should give you a more specific
error message for that particular provider."

Michael Akopov
@makopov
Have you installed VirtualBox?
Or in your case, VMWare
Jjemastr
@Jjemastr
I have it
Victor Meyer
@pudgereyem
Hey guys. The mailcacher gem needs ruby version 1.9.3 or above. How do I proceed?
Victor Meyer
@pudgereyem
@r8 I had problems running this on OS X 10.10. Also tried with develop-1.0 but did not work.
Alejandro Mangione
@alejandromangione
hi
I have a problem, when execute vagrant up, show me the message: There are errors in the configuration of this machine. Please fix
the following errors and try again: Vagrant: * Unknown configuration section 'berkshelf'.
Spir
@Spir
on linux how do you change VAGRANT_HOME? export VAGRANT_HOME=/some/new/path is correct?
I don't have enough disk space on /home
Pierluigi Cau
@pierlo-upitup
hi there! thanks for the great work. I'm a bit scratching my head on how to get additional domains to work. I've followed the instructions in the readme (https://github.com/r8/vagrant-lamp#apache-virtual-hosts) but I'm a bit unsure about what to do with the host machine (OSX Yosemite) /etc/hosts file
I've added a "192.168.33.10 local.dev" in /etc/hosts and it works (i see the phpinfo). Do I need to add a line for each new domain i want to add? For example, mytests.dev ?
Sergey Storchay
@r8
yes, unfortunately that's the only way to do it now: add all domains to hosts file
I'm thinking about supporting vagrant-hostmanager https://github.com/smdahlen/vagrant-hostmanager
But for now hosts file is the only way
Saurav Shrestha
@sshrestha-navarts
Does apache2 autostart even after you shut it down? (service apache2 stop)
James Pessato
@pessato
Developed an app on the vagrant-lamp stack. Time for production/deployment. Any recommendations? Is there a "production" version of vagrant-lamp?
egeogretmen
@egeogretmen
I seem to have permission problems for the host machine. After 'vagrant up', I have 403 Forbidden error when I type localhost:8080. I get "Server not found" when I type local.dev. I also cannot see the entry "192.168.33.10 local.dev" in the host machine's /etc/hosts file. When I add it manually and check from the browser, I get again 403 Forbidden. What may be the problem? Am I doing something wrong?
Sergey Storchay
@r8
Hi @egeogretmen. Are you using the latest version from repository?
egeogretmen
@egeogretmen
yep, it was funny because yesterday i was searching for a lamp stack then came across to yours and just around those times you were pushing to github
@r8
Christopher John Duncan Araúz
@cjduncana
Hello
Today, I installed vagrant-lamp but it gave me an error.
Christopher John Duncan Araúz
@cjduncana
The error was along the lines of chef should not have the following setting: nodes_path
I could not vagrant up because of this error.
In the Vagrantfile, I commented out chef.nodes_path = "nodes".
Now, it runs fine.
Christopher John Duncan Araúz
@cjduncana
I see that @r8 recently fixed issue #134 by adding that line to the Vagrantfile.
Christopher John Duncan Araúz
@cjduncana
Simply removing that line is not a solution. If that is done, we would just be opening the previous bug.
I'll check later to see if I can replicate the bug from issue #134.
Christopher John Duncan Araúz
@cjduncana
It seems that support for chef.nodes_path has been changing a lot. Refer to mitchellh/vagrant#6862
It seems that not all of GitHub Markdown is supported. *Refer to https://github.com/mitchellh/vagrant/issues/6862#issuecomment-187763515
Sergey Storchay
@r8
yeah, it seems that what works for Vagrant 1.8 will not work for 1.7 and vice versa
I'll check if I would be able to make that option conditional depending on Vagrant::VERSION value
still hacky, but hope it will work
Sotiris Katsaniotis
@Sotiris-k
Hey guys, can someone tell me where does the VM store the private_key at first setup?
Purevtsooj Davaatseren
@purevtsooj
I couldn==> default: [2017-05-09T07:47:28+00:00] ERROR: undefined method `set' for Chef::Platform:Class
==> default: [2017-05-09T07:47:28+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
i couldn't solve this problem
Anyone has this issue? and how did solve please help me guys
Jorge Jacques
@jjacquesf
anyone knows wich version of php is installed?
Md Jan A Alom Beg
@janbegjan
need help! php isn't running... "I've created public/local.test/index.php"