Member Since 1 Year Ago
1,050 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 Inserting Data Into Laravel Database From Non-Laravel App
I am developing an orders database in Laravel. It will consist of orders (billing and shipping info, etc) along with products that were ordered.
The orders will be coming from a non-Laravel website, hosted on the same server. Customers should also be able to do things, such as login to the non-Laravel website and check the status of their order.
I can easily make the non-Laravel website have access to the Laravel database for the purpose of inserting new orders, and retrieving the status of existing orders. However, I was wondering whether it would be better to make the Laravel application have an API? The non-Laravel website could then insert orders, and retrieve the status of orders, via the API rather than directly to/from the database. Do you think this is worthwhile, or is it an overkill?