4,910 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.
Replied to Is Passport For Me?
With public API I meant, will the user have to log in to consume the API (even if he does not know it) or will you be using the API for example, to fill out your public homepage?
From your response, it seems like the data you'll be sending is user-centric. I would personally go with JWT and session authentication because it's pretty straight forward to implement.
I am not sure I quite understand the problem. If you could enlighten me... here is what I understood:
1 - you store and work with Gregorian dates (database and controllers) 2 - you want to show Jalali Dates on your View
If I understood that correctly, then what you would need is, a blade directive to help you converting your Gregorian date to Jalali no?
I was suggesting taking a screenshot of the debugbar.
If you do not need "live data" - I would probably choose the second option.
You have a couple thousand lines, that should not be a huge hit on the DB, but when you get close to the hundreds of thousands or millions, aggregation can be very painful for the DB.
Replied to Is Passport For Me?
What are your business rules for the site? Are there any specific restrictions to your API such as transporting sensitive data? If you are essentially creating a public API and you'd just like to make it harder for somebody to gain access to it, then API tokens should be enough for you. If, on the other hand, you'll be using user authentication, transporting sensitive data and so on, then passport should be a better fit, since it will renew the token and require handshakes. Think of it as "Public API" vs "Facebook API"
If you can print out debugbar's output, we can have a better view of what's going on and help guide you into a solution. Also having a look at your system.log file might show you a number of unseen errors (specially if youve turned off debug in your .env file).
I would try and run the queries directly against the database (in a PHPMyAdmin or Workbench) to see how they perform. It can give you valuable information.
Finally, as @snapey mentioned, do watch Reinink's talk... it is a gem and gives you fantastic insights into how you can optimize your site.
there are basically two ways to go about what you want... one would be, as mentioned above, have the pages cached, and the other option would be to generate a static page for your home page every time you update the admin or at midnight through a cron (I must mention that this is essentially what caching is doing for you).
If you are talking about a very high volume site, you probably be better off using some caching service like cloudfare or similar, which would essentially be doing that for you.
Replied to Count One-To-One To One-To-Many Relationship
You can use the
withCount method from eloquent.
If you are getting a 404 it would imply your are being redirected somewhere. Check your logs to see if there is any 301s. I would start off by removing the auth middleware and see if the problem persists. The less moving parts you have, the easier to debug.