Member Since 5 Years Ago
1,335 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
It's important when trying to debug Homestead is that you share as much of the configuration and logs as you can, that's exactly why the Homestead repo has an extensive issue template to help people get the best help by providing the most information they can. I can almost always spot the issue from a complete log of:
vagrant destroy && vagrant up and a copy of
svpernova09 left a reply on Is Supervisor Installed By Default In The Homestead Box
You wouldn't upgrade supervisord with pip since we install it via apt-get. If the supervisor you get is from 2016, that's the most recent packaged in Ubuntu 18.04 at the time that base box was built. We build new base boxes at least every 2 months and sometimes even monthly.
The proper way to run multiple instances of Homestead is to use the per project installation method: https://laravel.com/docs/5.4/homestead#per-project-installation
svpernova09 left a reply on Homestead Vagarant Up Is Not Working On Windows Machine
This is a bug in Vagrant 1.9.3 on Windows. Add the line or downgrade back to 1.9.2. It's been fixed but waiting on a release of 1.9.4.
Planning on releasing Homestead 5.0 next week. What would you like to see done?
You can see just about everything that's coming so far by looking at the commits since version 4.0.5: https://github.com/laravel/homestead/commits/master
Some of the incoming changes:
.homesteadfolder. Files will be in the same folder you cloned Homestead
share()alias for really easy public URLs for your projects.
If you're having issues with this, open an issue on github: https://github.com/laravel/homestead/issues/new
Laravel no longer supports HHVM (since 5.2 or 5.3). It's still in Homestead because it's more effort to pull it out than leave it in. It will probably be removed soon™.
It sounds like your folder mappings aren't correct. I would double check your folders and sites mapping.
SSH into vagrant and run
sudo service mailhog restart and you should be able to view http://localhost:8025
Map each site as it's own folder in your folder's mapping.
folders: - map: F:/Php/Laravel/homestead.app to: /home/vagrant/homestead.app - map: F:/Php/Laravel/runner.app to: /home/vagrant/runner.app sites: - map: homestead.app to: /home/vagrant/homestead.app/public - map: runner.app to: /home/vagrant/runner.app/public
I would have to see your Homestead.yaml, and full vagrant up output be much more help.
Make sure you're running Virtualbox 5.1 and Vagrant 1.9x and using Homestead 1.0.x If you're doing all these things then open an issue and fill out all the info here: https://github.com/laravel/homestead/issues/new
phpunit isn't installed globally. Since you're using the per project install method of Homestead when you run the make command you have to specify the aliases options to get the aliases file added which has the shortcut of
To get this file run:
php vendor/bin/homestead make --aliases and you will see an aliases file show up in your project root. This will be copied into Homestead by running
vagrant provision or
vagrant destroy && vagrant up
Homestead.yaml try wrapping your paths in quotes
While running commands from within Homestead should be limited (Since you'll obviously have more RAM on your host OS than Homestead) I can empathize.
Grunt CLI missing seems like an oversight. I'll get it added. Will require a box update, so in the meantime if you want to run from within Homestead you'll need to
sudo npm install -g grunt-cli.
composer require "laravel/homestead" "^4.0" --dev From @acm4b's previous comment. So you get version 4 instead of 3.
The proper commands to run to install per project:
composer require "laravel/homestead" "^4.0" --dev php vendor/bin/homestead/make vagrant up
It's not 5.4 but if 5.5 will work:
You need to use a different box. The default box is broken. (I'm currently writing a blog post that explains all of this)
And use version 2.1.8 of the Homestead Source Code (The Github Repo)
Ask your customer if they instruct their plumber on which tool to use for fixing their problem. Ask if they instruct the car mechanic on which brand of wrenches to use.
Laravel is a tool in your toolbox. It's not right for every job. Tooling is your choice as a developer. You should be making these decisions based on the customer's requirements, not their google search on who knows what.**
** Unless your Customer is a more advanced PHP developer than you are.
Check out https://24pullrequests.com You can sign up for an account and select Languages/Technologies you'd like to work in and they have tons of projects listed for you to check out.
And why not PHP itself?
I don't know of any wireless backlit keyboards. If you don't mind the wire I'd recommend a Razer Blackwidow Ultimate keyboard. It's a full size mechanical that comes with either blue or brown switches. (Blue are clacky in sound, brown have the similar feel, but not the clack). You can usually find these for ~$100(US) on Amazon.
The issue is likely your webserver is bound to a private IP that only your desktop has access to. This is what Homestead uses out of the box.
To fix this, add a
public_network to your vagrant. If you're using Homestead, you can see how to do this in the docs: https://laravel.com/docs/5.3/homestead#network-interfaces
Warning This will expose your vagrant to your local network. Since Vagrant is inherently insecure it would be an easy target.
If you're trying to use PHP 5.x with Homestead, the version of
laravel/homestead box is currently broken (the mysql password has expired). You can use the box named "Svpernova/homestead-legacy" with Homestead 2.2.1.
Homestead.yaml would look like this:
box: "Svpernova/homestead-legacy" version: ">= 0.3.4"
This is incorrect:
The name of the box is only "laravel/homestead"
v4.0.2 was just tagged, so you can go back to master with
git checkout master && git pull origin master or checkout the new version with
git checkout v4.0.2
It's a bug in version 4.0.1, Which is why checking out the 4.0.0 tag fixes it, you rolled the repo back 1 release. I'll tag 4.0.2 shortly and then you'll be able to do
git checkout master && git pull origin master if you want to go back to using master.
Master is bleeding edge. Always the latest stuff. If you want to stick to stable releases you can checkout a release tag, which are version numbers such as
v4.0.0. You can find releases here: https://github.com/laravel/homestead/releases
Looks like you've found a bug! For a quick fix try running this in the folder that you cloned the Homestead repo:
git checkout v4.0.0
vagrant provision and you should be all set. I'll get a fix merged shortly.
Will you run
vagrant provision and paste the output. Thanks!
Can you post the entire results of
vagrant up, your
Homestead.yaml file, and what version of the Homestead software you're using?
Homestead 4.0.1 has been released to address a problem on Windows where editing the aliases file in an editor that does not properly respect existing line endings would cause issues installing the aliases file in the virtual machine.
Something might have gone weird with your Vagrant install. I would try reinstalling Vagrant. Haven't seen anyone else with this. Don't think it's homestead related unless you've edited Vagrantfile with something that is breaking Ruby syntax.
Follow the official doc next time. @ejdelmonico had you wipe everything and start over from scratch. Not always a bad idea, just more effort.
Hot off the Pull Request- Official Docs for Updating Homestead: https://laravel.com/docs/5.3/homestead#updating-homestead
The current version of Homestead is 4.0 which requires a the box version ~1.0. This box is Ubuntu 16.04 and PHP 7.1
If you need PHP 7, use Homestead 3.1 and box version 0.6.0 (Ubuntu 16.04)
If you need PHP 5.5, Use Homestead 2.x and box Svpernova09/homestead-legacy (Ubuntu 14.04)
Box version 1.0.1 released that adds missing XDebug.
@Aleh Looks like you found the first bug in this release!
php-xdebug isn't installed :/
Will fix and update.
We released Homestead 4.0.0 this morning along with a box update to version 1.0.0 (Virtualbox AND VMWare).
Homestead 4.0.0 requires box 1.0.0 since we're upgrading to PHP 7.1
Not sure how to update? Want to stay at PHP 7.0 for a bit? Instructions here: https://www.joeferguson.me/laravel-homestead-4-0-and-box-1-0/
This morning Homestead 3.1 was tagged. Due to a version numbering mishap it might be a significant jump for you. I’ve tested it with OS X: Vagrant 1.9, Virtualbox 5.1.x, VMWare Fusion 8.5, and Heard success from Windows 10 + VMWare Workstation
You’ll almost certainly want to make sure you’re using Vagrant 1.8.6 or 1.9 AND destroy your current box & ensure you
ou `rm -rf .vag folder in the Homestead directory if you run into issues.
Also this morning I released an updated Homestead box 0.6.1 for the VMWare provider only. This should address the following error:
==> default: Waiting for HGFS kernel module to load... The HGFS kernel module was not found on the running virtual machine. This must be installed for shared folders to work properly. Please install the VMware tools within the guest and try again. Note that the VMware tools installation will succeed even if HGFS fails to properly install. Carefully read the output of the VMware tools installation to verify the HGFS kernel modules were installed properly.
The previous issues we've seen have likely been caused by
open-vm-tool no longer containing the script to install the VMWare tools in the Guest OS. The new box manually installs these tools.
svpernova09 left a reply on Is Queuing Necessary For Commands Run Via The Scheduler?
Ah, I see. No it shouldn't matter.