I'm new to vagrant and followed along with the getting started tutorial and was able to initialize and run the precise32 box and serve a "hello world" index.html file from http://127.0.0.1:8080.
However, I want to run a PHP box so I grabbed the most popular LAMP box (scotch/box) off the vagrant cloud.
My problem is that when I run the setup command for the LAMP box:
vagrant init scotch/box; vagrant up --provider virtualbox
The box does not appear to boot up and instead I receive the following message:
Authentication failure. Retrying...
I have a brand new Virtual Box install (5.0.6) am on OSX (Yosemite) and I'm not trying to do anything out of the ordinary, just run a PHP machine. Any ideas where I'm going wrong?
I have no idea why several of the most popular boxes would not work for me... but for anyone else who comes across this, I just tried several boxes until I found one that actually worked as advertised (at least with my configuration). The box that worked for me was: smallhadroncollider/centos-6.5-lamp
Here are the full steps I took to create a working PHP environment using vagrant:
Install VirtualBox
Install Vagrant
Add a new vagrant box: vagrant box add smallhadroncollider/centos-6.5-lamp
Create new empty directory and navigate to it within terminal... once there, initialize your new vagrant box: vagrant init smallhadroncollider/centos-6.5-lamp
Edit the auto-generated vagrant file which was created in the directory where you just ran the vagrant init command and comment-in the "forwarded_port" setting to allow host machine port 8080 (or whatever port you choose) to route to virtual server port 80.
Start-up your new vagrant box: vagrant up --provider virtualbox
Create index.php file in the same directory as your vagrant file. Run it from http://127.0.0.1:8080 and it should process your PHP code
Now, enable debugging messages by SSHing into your new vagrant box with vagrant ssh
Enable debug output by editing php.ini on your vagrant machine (/etc/php5/apache2/php.ini) - if necessary, find where php.ini is stored using the phpinfo() function in your index.php file
While still on vagrant machine, restart Apache sudo /etc/init.d/apache2 restart. Ignore the "could not reliably determine... warning message."
exit vagrant box to return to your local machine. You're done and your PHP code should now be running with debug messages.
Related
I got a php project which is already done and for starters I have to put it up on a server (planning to use Heroku). I am new to PHP virtual boxes, Laravel, etc. The person who made the project recommended to use Laravel so I started to get things going that way. I am running on Windows 10 and using cmder as my terminal.
I downloaded VirtualBox & Vagrant.
Then using commander I added the Laravel/Homestead box
by doing:
vagrant box add laravel/homestead
in the folder c:\Users\Jacky\vagrant\ubuntu (At least I think that is where I added it)
Afterwards I believe I did
vagrant init
or vagrant init laravel/homestead
whatever I did afterwards I was able to run
vagrant ssh
and get into the system. There I was able to check and I had php and composer installed.
I then followed laravels instructions and created a homestead folder at c:\Jack\Homestead
ran git checkout for v7.19.2
ran init.bat
and configured the Homestead.yaml file
I made the following folder map
- map: C:\Jack\myapp\public
to: /home/vagrant/myapp
and the following site map
- map: myapp.test
to: /home/vagrant/myapp/public
I am a bit confused with the directory structure of this whole thing and not sure if I was supposed to put the myapp directory inside c:\Jack\Homestead\myapp or if just doing it like i did in c:\Jack\myapp is fine.
Anyways that still worked and I could see it in my web browser. So far all was good.
Then the project instructions told me to do the following
run composer install
There was an env.example file I had to change to .env and change some setting
run php artisan key:generate
run php artisan migrate --seed
run php artisan passport:install
run php artisan storage:link
At this point I got an error that the Symlink could not be created, so I googled and found in Stack Overflow to restart as admin. I ran cmder as admin and have been having a heart attack for the last 30 minutes since it told me I had to vagrant up and when I did so it couldnt find my box and even doing vagrant box list
I would get no results and it wanted to redownload which takes over 3 hours.
I just restarted without admin and I do find that my Laravel/Homestead box is listed so I assume it was installed for my user and not admin so I guess I cant run cmder as admin.
So now I am trying to connect again, I am not sure in which folder I should be running the vagrant commands but I only seem to have a VagrantFile in my C:\Jack\Homestead folder so if I run a vagrant command anywhere else it gives me an error that a vagrant environment is required, etc.
So I tried the following inside my homestead folder:
vagrant ssh - I get:
VM must be running to open SSH connection. Run `vagrant up to start the virtual machine.
(In my VirtualBox Manager i see my homestead-7 VM running though)
vagrant up - I get:
Bringing machine 'homestead-7' up with 'virtualbox' provider...
==> homestead-7: Importing base box 'laravel/homestead'...
==> homestead-7: Matching MAC address for NAT networking...
==> homestead-7: Checking if box 'laravel/homestead' is up to date...
A VirtualBox machine with the name 'homestead-7' already exists.
Please use another name or delete the machine with the existing
name, and try again.
vagrant ssh 'homestead-7' I also get
VM must be running to open SSH connection. Run vagrant up
to start the virtual machine.
And the problem is once I do connect I assume I will still have the same problem running:
php artisan storage:link
So my questions are as follows:
Where should I have my projects myapp folder, should it be where it is at C:\Jack\myapp or am I supposed to put it in C:\Jack\Homestead\myapp
Is the VagrantFile supposed to be only in my Homestead folder and is that where I should be running all my Vagrant commands from? Like vagrant ssh and vagrant up
How do I connect again now that I am getting those errors running vagrant ssh and vagrant up
Once I connect I assume I will get the same error running php artisan storage:link since to run as administrator seems to not work what do I do?
I Assume that I should run git init and heroku create inside the myapp folder is this correct?
1) I always keep my apps folders outside of the Homestead folder. Your Homestead folder contains a git project, so if you put your apps inside you should include the folder in the .gitignore file. I think it's easier if you just put your apps elsewhere.
2) Vagrantfile is suposed to only be inside of your Homestead folder ( c:\Jack\Homestead). You should run all your vagrant commands inside the Homestead folder.
3) I used to get this error when I tried to run 'vagrant up' to a project that used the same box name 'homestead-7'. If you have version control, check if the file c:\Jack\Homestead\.vagrant\machines\homestead-7\virtualbox\id has been changed. If so, try restoring the old value and running 'vagrant up' again.
4) You are running in a windows environment, right? Windows can be a little temperamental with symlinks inside vagrant. You'll get the same problem if you try to npm install something. What I do to solve this is to run npm (and php artisan storage:link) outside of the virtual machine, in the host pc, inside the root of the app folder. Just a reminder: to do that you will need php installed in your host machine.
5) All commands related to the app (and not the virtual machine) should be run inside the virtual machine, in the folder app (ex: /home/vagrant/code/myapp) or inside the app folder of your host machine. Those two folders are in sync, thanks to vagrant.
I have followed the steps on Laravel's website, to install Homestead, through VirtualBox.
Install Virtual Box (through their package)
Install Vagrant (through their package)
Run vagrant box add laravel/homestead
Within my application's directory, run composer require laravel/homestead --dev
Run php vendor/bin/homestead make
All of the console output shows a success for the above. I can see the Homestead.yml and Vagrantfile files within the app's directory.
When I run vagrant up, I then get this error:
The VirtualBox VM was created with a user that doesn't match the
current user running Vagrant. VirtualBox requires that the same user
be used to manage the VM that was created. Please re-run Vagrant with
that user. This is not a Vagrant issue.
The UID used to create the VM was: ** Your UID is: **
I'm unsure why this has happened, as I haven't used sudo, nor switched between.
Also, within Virtual Box's preference, it shows the default install location of boxes to be in: /Users/AccountName/VirtualBox VMs, but that directory doesn't exist.
However, Vagrant will list laravel/homestead as a box that's installed.
I'm unsure what exactly the problem is.
Please help!
You have to run vagrant up command into ~/Homestead directory.
I tried setting up a virtual machine using Homestead box. I followed documentation on Laravel site for setting up Homestead.
When I ran the command vagrant up, it seemed to work in setting a VM. Then it asked to run vagrant provision, which I did.
I can't get pass red text 'You are already using composer version 1.1.3 (stable channel)'. I don't know what to do next.
Update: here is Homestead.yaml file:
Needed to edit the file at
~/.homestead/Homestead.yaml
instead of
~/Homestead/Homestead.yaml
after that reload it as usual
vagrant reload --provision
Add
~/.composer/vendor/bin
to Your PATH on host machine (not inside vm).
After restart terminal You can use homestead command.
I was wondering how I would be able to run multiple versions of homestead without having VirtualBox crash.
I am currently running a default installation of the laravel homestead, but I need to install another custom one, which is customised to work with several proxies.
Just to be clear: I know how to run multiple sites. That is not the issue. I just want to run a second, custom version of the Laravel Homestead Vagrant box, while still having the possibility to run my normal one.
Details: I'm running Homestead v2.1.7 on Mac
Thanks in advance!
I know it's an old question, but the problem is still accurate.
There are some circumstances when you have to run two instances of homestead at the same time. For example when you have app that is works with apache, and one that is freaking out when you enable apache on a server. When you enable it on one website in Vagrant.yaml it will redirect every page that is not using apache to the site that is using it, see example:
- map: presta.shop
to: /home/vagrant/htdocs/presta-shop
type: apache
- map: my.app
to: /home/vagrant/htdocs/my-app
In this situation when you will call my.app homestead will redirect you to presta.shop - because this site is using apache (PrestaShop needs to run under apache). See this link: Github NGINX and Apache conflict #555
My my.app will crash with apache enabled, or I just don't want to enable it on this app, or I just need one extra server just for testing or something. You have to follow those steps from install homestead. After the installation of first server you need to:
run VirtualBox (or other machine you are using)
find and rename added homestead box (homestead), to what ever you wish ie: apache_homestead
go to homestead dir (cloned from git)
find file: Homestead.yaml
in Homestead.yaml add new line after provider with name (this is the name of your
renamed box apache_homestead in this case), and ip for let say: 192.168.10.11
in this file you can configure many settings, including name:
ip: "192.168.10.11"
memory: 3072
cpus: 1
provider: virtualbox
name: apache_homestead
After that You may change name of a dir where homestead clone is (default name is homestead). If you rename it to homestead_apache and run vagrant up from this directory you will have completely independent server.
To run "normal" server just follow the instructions from install homestead again and run as many servers as You wish :) Run any just go to it homestead directory and run vagrant up. Remember the limitation of your host machine!
IMPORTANT NOTE!
You can have all files for all servers in one dir, but every server has it's own database!!. So before you will move application to another server export and import it's database!
I did a global install of Laravel homestead, edited my ~/.homestead/Homestead.yaml-file and spun up the VM with homestead up. Everything worked fine, but then I needed to add another site. I edited Homestead.yaml to contain the new project, the tried to run homestead provision to apply the changes to the VM. The only thing that outputs is:
==> default: VM not created. Moving on...
I interpret that as the VM is not running, but it is. The only thing working here is homestead destroy followed by homestead up, but that (by its nature) detroys the VM's saved state. I though that vagrant commands was applicable to homestead as well, but vagrant suspend && vagrant up --provision doesn't help.
So.. How do I apply my new config to an already-existing homestead VM?
I found the answer at Laracasts. Copied directly from there:
Try doing this... You should see a vagrant box that is listed that is linked to your composer/vendor...
vagrant global-status
Example Output:
$ vagrant global-status
id name provider state directory
-----------------------------------------------------------------------------------------------------
1ace413 default virtualbox running (...)/laravel/homestead
Then go ahead and run:
vagrant provision {ID}
Example input:
vagrant provision 1ace413
ID being the id of the vagrant instance in the above step.
You should then be good to go!
I recently change my laptop from 32 bit to 64 bit and have to redo installation and setup of my Homestead again.
After setup everything I run below command
vagrant reload --provision
and I get the same feedback which is
==> default: VM not created. Moving on...
After that I try this command and all works well.
vagrant up
I think for first time running Homestead, no need to reload --provision.
You can run vagrant provision to update homesteads websites. However you have to find where the Vagrantfile for the Homestead VM is. If you did the global install it should be in .composer/vendor/laravel/homestead/ directory. You need to change into that directory
cd ~/.composer/vendor/laravel/homestead
Then you need to provision the VM
vagrant provision
Your homestead box should then reflect the changes in the Homestead.yml file.
Edit: I am not at my mac right now so the directory path is a guess of what I remember it being the last time I provisioned my box so please take that into consideration but I am very sure that path should be correct.
I had my VM provision vertualbox running
so i had to exit first