A new monthly tradition continues - here are 10 packages I've found this month, thanks mostly to Twitter and Laravel News blog. Uploading this as a SlideShare presentation, which I will present at my local Laravel meetup tomorrow, but you guys will be the first ones to see it. Also I will provide the links to actual packages below. Enjoy!
A few times I encountered a situation - a store() or update() method with Request parameter, but I needed to add some additional value to the request before calling Eloquent functions. So how to do that? Apparently, pretty easy.
There are two "tricks" I want to show you here. Probably you will know one of them, but might not know the other one. So, you know there are fields created_at and updated_at in Eloquent tables, right?
This article is a personal one from me and I really need your opinion on this idea. Would be grateful for any feedback in the comments, on Twitter or email [email protected]. So, in short, does the market need QuickAdmin in SaaS version?
Here's the 2nd episode of my new Laravel Business video show where once a week I share the thoughts about Laravel-related work from the business perspective, as I'm transitioning from being a developer to being an owner of a small team.
There's so many Laravel packages out there! Around 8500, to be exact. And so many of them unknown to the public, because authors are not shouting about them too loud. So I decided to help them and start a monthly digest of less-known packages, presenting them at my local meetup in Lithuania, and also on the blog. So here's 10 packages I've found this month.
One of the most common questions in Laravel world is how to organize the routes file, especially for bigger projects. Of course, you can have groups, prefixes and similar things, but today I want to present to you a package by Sebastiaan Luca - called Laravel Router.
After all those recent Mandrill news the whole web-dev community was shaken up and started looking for alternatives for transactional emails. And actually, there is a whole another way of thinking about it: do we always actually need to send the email?
One of the problem with database migrations in Laravel is developers rarely actually test "down" migrations - even when testing we usually re-generate the whole schema from scratch instead of launching down() functions. Therefore I would advice to check something before doing down migrations.
