2,715 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.
Started a new Conversation How To Host A Laravel Application At A Route Of Another Laravel Application?
I have a Laravel application hosted at mydomain.com, and now I have another Laravel application that I would like to host at mydomain.com/email. I went through a guide on https://serversforhackers.com/c/nginx-php-in-subdirectory and it made a lot of sense to me, and worked perfectly.
But the company I work for uses Apache2 on production and I am trying to translate this configuration to apache 2. But I am not sure how.
Here is what I have done so far. I have added
Alias /email /dir/of/nested/laravel/app/public to my main laravel application's apache config.
With this the routes on mydomain.com/email no longer show a 404 from Laravel side, but now they are being redirected to the nested application, I know this because going to mydomain.com/email redirects me to mydomain.com/email/login. But now I trying to figure out what do I need to change in the .htaccess of the nested Laravel app to make the work, because I see a 404 from Apache on all routes of
Any ideas anyone? Will it require some kind of a Rewrite rule?
Also how good is this is solution? Will I be restricted to one server because of this? Will it be scalable?
In one of the forums, I saw someone mention that they had a similar architecture, but they used a load balancer to redirect all the nested laravel app routes, is that a better solution than this?