Hey guys, I've broken the silence - first article on Laravel Daily blog in almost a month! See below the link about uploading multiple files.
Also, I've been asked how much time I spend on collecting the links for the newsletter and how I do it, in general, so it's pretty simple but hard work: - A few times a day I scroll Tweetdeck for search results for "laravel" - If I find a useful article - I add it to Buffer for tweeting via @DailyLaravel or @QuickAdmin, also on our Facebook Page - If that article is VERY useful and deserve a place in the newsletter - I add it to Pocket with tag "laravel" (using Chrome extension button) - And then I use my own created tool LinksLetter.com (built on Laravel) which uses Pocket API and prepares HTML template to send to Mailchimp API. I could do that myself manually, but it would take a few hours instead of 5 minutes.
Does it sound complicated? A lot of tools, huh? It totally takes around 30 mins a day to find/save links, and then 30 mins to send a newsletter (including writing intro like this). I hope you're grateful for thos couple hours a week of my time :)
And now, let's get to this week's articles!
How To Upload Multiple Files in Laravel 5.4
laraveldaily.com
File upload is one of the most commonly used features in web-projects. And it seems pretty easy – form, submit, validation, store. But it gets a little more complex if you want to allow your users to upload more than one file with one input – let’s see how it’s done in Laravel.
Laravel Paystack Curl Error
medium.com
After a really long hiatus, I decided to go back to coding. It was my first and only real love. I had been working about a decade in Data Center and Enterprise Infrastructure. I knew I would go back someday. The desire had been gnawing my heart, until finally I gave in. Enough of that.
Simple site launch checklist checker/validator.
github.com
After (or is it before?) lanching a new site, you often want to validate it against a checklist and make sure the title is filled, gzip is enabled, robots.txt and sitemap.xml are all there etc. kupo is built to help you with this tedious task.
Laravel Command to Generate Swagger Documentation
aaronsaray.com
If you’re not using Swagger (or OpenAPI) yet to document your APIs, you should start. It’s pretty simple to get started - especially in PHP. I recommend using the swagger-php package - it’s pretty easy. Just use annotations, and then generate the Swagger definition when you’re done.
Laravel’s tap helper function explained
medium.com
A little known helper function, called tap was added to Laravel 5.3. In this short post I'll explain how this function can be used. Let’s first take a look at the tap function itself. It's actually a very short one.
Laravel 5.5 Will Be The Next LTS Release
laravel-news.com
Version 5.1 was Laravel’s first LTS release and its two-year window of bug fixes are coming to an end this year. There have been a few people questioning if another LTS would be released and version 5.5 would be the next in line if it did happen. Laravel 5.
Convert MailMessage to Mailable in Laravel 5.3+
medium.com
The Notification system in Laravel 5.3 makes it easy to send a single block of notification content to multiple channels. I ended up using it mainly to send quick action-oriented mails, since I really liked the drop-dead-simple MailMessage builder:
Zero Downtime Laravel Forge Deploys
medium.com
So you’re a Laravel developer and of course you are using Forge to manage your servers. You enjoy how simple Forge makes it to deploy your applications but you may notice a few seconds of downtime when your app is updating packages etc.
Setting up local step debugging with PhpStorm
www.geekyboy.com
Setting up debugging in an IDE with a local development environment has gotten so easy it can be done in a few automated steps. In this post I will demonstrate how to get step debugging functioning with PhpStorm and Zend Debugger when the server is set up on a local environment.
A bit of PHP history
toys.lerdorf.com
Ran across this Changelog from a long long time ago. Read from the bottom up. I added the PHP Tools lines at the bottom for context. So many early decisions made on a whim still affecting us today. And then there are things like "Removed **, // and %% operators" which did a vector dot-product and its inverse, I think. I seem to recall deleting it when I tried to document it.
That's it for this week, see you next Thursday for the new issue! Povilas Korop Laravel Daily Team
|