One of the final steps in every web-project is deploying to live server. Often I see a problem when server is provided by the client from their hosting they had purchased long time ago, and it is not suitable for convenient Laravel deployment. So in this article I will make some recommendations for clients, what hosting to prepare.
Sending email is a typical function for most web-projects: notifications, password reminders, invoices are done via email. But in recent years we've faced a technical problem. It's not about just sending emails anymore, it's about delivering them successfully.
Laravel-Excel package is great for exporting data. But not a lot of info there about formatting Excel cells - widths, word wraps, fonts etc. So when I encountered this in a client's project, I decided to write this article with a few tips on this topic.
With Laravel Live UK 2018 being over (awesome event, thanks Jonty!), I want to share my recap of one particular talk. Matt Stauffer has expressed his thoughts about Laravel in enterprise world. Is Laravel good enough? Let's find out and discuss.
Recently I've started a new client project which uses API of a project management tool called Asana. So I decided to write up a short demo for anyone who wants to use it, it's really simple.
Recently popular package Laravel-Excel released a new version 3.0, which was a pretty radical change from previous versions. I needed to do a simple Excel export and noticed that their documentation covers only export from Laravel Collections but not from some custom structure. So I will show you a "workaround".
For some reason, only now I've found out about a feature that was introduced in Laravel 5.5 - artisan command that makes your validation rule, similar to Request classes. Let's see it in action.
Quick tip of the day. Default Laravel Auth comes with User table and model, but without logging capability, so we need to build it ourselves. Fortunately, it's very easy, I will show you one method.
Quite often web-developers don't care enough about errors. If something goes wrong, you often see default Laravel texts like "Whoops, something went wrong" or, even worse, the exception code, which is not helpful at all to the visitor. So I decided to write a step-by-step article of how to handle errors in elegant way and present proper error information to the visitor.
Not sure if you've noticed, but Laravel 5.6 make:auth is generating Blade files with translation-ready texts, so instead of just "Login" you will see {{ __('Login') }}. How does it work and what's the reason?
