3,425 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.
Eldair started a new conversation How To Stop/return From Queued Slack Route Notification
This is how I dispatch notification
Notification::route('slack', $slackHook)->notify(new SomeNotification($companyId));
Since the notification is going through the queue it can happen for the company whose ID was sent to be deleted in the meantime. I couldn't find how to stop
toSlack method in those cases since it requires
SlackMessage as the return type and throwing an exception is just going to retry job.
Hello, a question for everyone testing Laravel 5.3, are controllers now constructed before route middlewares fire? In Laravel 5.2 I had auth user available in controller constructor when the auth middleware was defined in routes file but now I don't.
Hello, @pdcmoreira I can include your steps into accepted post or set it as accepted, even though I haven't tried it, it is easier solution (: Is virtualbox 5.0.1 now working correctly? I don't wish to update/loose my currently working setup if it's not completely ready :/
@bogdanus try to reinstall virtualbox, because it should have created one during installation. If not, try installing as admin. @vnobre the :8000 can be avoided if you change default port forwarding 80 => 80 instead of 80 => 8000 in homestead.rb or go to settings of your box -> network settings -> adapter 1 (nat) and port forwarding option, and there you will see port 80 forwarded to port 8000, change it to 80 and that's it.
Hi @vnobre, to me it seems like you haven't commented out lines in action.rb and homestead.rb. You should do that and manually set networks for existing box after which homestead up should work (with mapping from homestead.yaml file).
P.S. I don't know why, but I had to add :8000 to alias urls in browser to get them to open pages.
Edit: the :8000 can be avoided if you change default port forwarding 80 => 80 instead of 80 => 8000 in homestead.rb or go to settings of your box -> network settings -> adapter 1 (nat) and port forwarding option, and there is port 80 forwarded to port 8000, change 8000 to 80 and that's it.
And it's working (: Cheers
UPDATE Alternative solution by @pdcmoreira:
I found a VERY SIMPLE way to make it work without touching any file in the accepted answer!
Install and run this file: https://www.virtualbox.org/attachment/ticket/14040/VBox-Win10-fix-14040.exe (leave it running in the background) Go to the C:\Program Files\Oracle\VirtualBox folder, right click on VirtualBox.exe, go to compatibility, check the "Run in compatibility mode" checkbox and choose Windows 7. Click OK to close the window. Repeat step 2. for VBoxManage.exe and VBoxHeadless.exe Run cmd and do homestead up. There you go! It should work!
After all is done and working, close the program opened in step 1.
You don't need to run cmd as Administrator in step 4.
In order to stop it from clearing existing network config you should comment line 64
in file action.rb located in ~\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.4\plugins\providers\virtualbox\action.rb
Hope this helps. P.S. even with this I couldn't setup Homestead on windows 10 with virtualbox 5 due to some error with mounting shared folders.. Still looking for some solution. Edit: Mount problem was with Vagrant 1.7.3, upgrade to 1.7.4 fixed it
Hi, I managed to use Vagrant for VB5 and to install it as suggested. When I start the box from Virtualbox gui it runs until "waiting for network.." message and stops there (via Vagrant - same error as above).
I am having issues running homestead via virtualbox on Windows 10 TP 10130 with error code
There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below. Command: ["hostonlyif", "create"] Stderr: 0%... Progress state: E_FAIL VBoxManage.exe: error: Failed to create the host-only adapter VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available) VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp
I am aware it is a common issue but was curious if someone has found a workaround?