Been looking forward to this podcast, Laravel in relation to real businesses out there.

In our very first episode, Matt had the pleasure of speaking with Ian Landsman, affectionately known as the 'Godfather of Laravel,' where they discussed his long history with Laravel and his business journey. Ian shared insights into his primary venture, UserScape, and its flagship product, HelpSpot, a help desk application he started 20 years ago. They also talked about taking a bet on Taylor and Laravel early on, bootstrapped startups, and more

Building a #jsonapi in #Laravel? I created an example API with features & packages I've found really useful! https://t.co/22ysAP7tvU #php

No problem with form requests, I like form requests, I'm just providing an alternative approach, especially for Lumen users who don't have form requests. If it's a simple API I find the config approach works really well, if I have to override the authorize() function or need to add an After Hook I use form requests for that app.

If the single config file gets too unwieldy, you could turn it into a folder /config/validation/ and then have a file for each object type post/author etc.

Reduce Validation Bloat in Laravel Controllers https://t.co/J2KXIkjA5o #laravel #protip

Recently ran into a situation using jwt-auth for Laravel where deleted users were causing errors because after deleting the user the auth token was still valid in redis, whoever the user no longer existed in the database, so when there was any calls to $auth->user() or Auth::user() it would error out when trying to make calls against that user object because false is returned.

When a user was deleted we should call $jwtAuth->invalidate($token) for that user but that's not gonna help us now that we have a bunch of other users who were deleted or if you need to delete users from DB manually.

I didn't want to have to check that calls to the Auth guard would not return false all over the place where I used the auth guard, so I looked for another answer.

Solution

Well it turns out others must have come across this issue as well because a merged PR to the project added a function to JWTGuard to throw a UserNotDefinedException if the user is not found. They didn't replace what happens when the user() function is called in order to stay compatible with how laravel's default guard returns false if not found. So use userOrFail() any place you normally would have used user.

You might have this happen to you if you switch back to an old project using Homestead. Basically you have a new version of the laravel/homestead vagrant box (1.0.1) which includes php 7.1 but the package in composer ^3.0 is expecting php 7.0.

Solution

Just add the line version: 0.6.0 to your homestead.yaml to indicate you want that version for the vagrant box which is the last one that includes php 7.0.

Binded by Gulp workflow Admin Dashboard Boilerplate. Plus Oauth and JWT authentication on the side.

The issue is that doctrine is keeping the objects in local memory because the daemon is basically a php long-running process. In order to allow the objects used by the job to get updated, you need to $em->detach() the objects. But you'd also have to have cacade={"detach"} on all relationships that object has as well. So the best thing is to just call $em->clear() at the end of your job. This will detach all objects from doctrine and it will get a fresh copy of all the objects from the database for the next job run.

This new NodeJS framework was inspired by Laravel, with similar folder structure and includes IOC container, very similar router, service providers, middlewares, even Views similar to blade. Utilizes ES6 classes for controllers. Even has an ORM called Lucid.

With long running processes you can get a 2006 MySQL server has gone away error. This adds a class that calls Doctrine's DBAL Connection's $conn->ping() to see if it's gone away, if so close the connection and let DBAL automatically open a new connection on the next query attempt. This is talked about in the Doctrine's Github repo here. Here's some pseudo code on how to do it:

<?php

namespace Acme\Doctrine\ORM;

use Doctrine\ORM\EntityManager;

class ConnectionSaver
{
    /**
     * Ping the DB server, if connection is lost close it and DBAL will
     * automatically reconnect on the next DB call.
     */
    public function checkDatabaseConnection()
    {
        /** @var \Doctrine\DBAL\Connection */
        $conn = app(EntityManager::class)->getConnection();

        try {
            $ping = $conn->ping();
        } catch (\ErrorException $e) {
            $conn->close();
        }
    }
}

Then inside the command handler you just inject the class and call checkDatabaseConnection() function.

<?php

namespace App\Listeners\Commands;

use Acme\Doctrine\ORM\ConnectionSaver;

class FooHandler
{
    public function __construct(ConnectionSaver $connectionSaver) {
        $connectionSaver->checkDatabaseConnection();
    }

Several php packages to easily integrate Doctrine 2 into your next Laravel/Lumen project. The 'orm' package includes a ServiceProvider to add Doctrine to your project and configure it. The 'extensions' package includes several extensions including timestampable, softdeletable, etc. The 'migrations' package add ability to use Doctrine's migration package instead of laravel's migrations so that you can easily take advantage of auto migration generation based on entities. The 'ACL' package includes traits to add roles and permissions to user objects to easily integrate with Laravel's new ACL.

This video tutorial goes over [one way] you can add the ability to give user's roles and specify which permissions those roles have. You would have to build upon this further to include additional features such as role inheritance or user-specific permissions (overrides).

Occam's razor, holds true even in programming.

Laravel's extreme success and popularity can be reduced to a single word: simplicity. Surprisingly, however, writing simple code is no easy feat! This talk will discuss key decisions that led to Laravel's success, while, in the process, reviewing a number of lessons-learned from over-architecting applications.

Speed up your website by caching entire responses. By default it will cache all successful GET requests for a week. Can store cache in any Laravel supported cache (file, redis, memcache). You can have separate caches per user. If you want more granular caching like ESI includes or reverse proxy caching check out laravel-httpcache.

Add a route to your site/app so you can view the logs files to view errors and anything else your app logs.

This allows numerous providers to be used in addition to the ones provided by Laravel Socialite (and they can be overridden easily). You can also easily create your own new providers.

Although Laravel now ships with an asset manager; Elixir, maybe you're in a situation you can't use NodeJS or you'd be more comfortable with a PHP solution instead of NodeJS. Laravel Potion also has the added benefit of CDN support built in which Elixir does not.

Doctine requires a custom made cli-config.php file for Setting up the Commandline Tool with a Laravel 5 application. The CLI tool is necessary when you need to for example clear Doctrine Cache using php vendor/bin/doctrine orm:clear-cache:metadata.

The following is what you can put in your cli-config.php:

<?php

use Doctrine\ORM\EntityManager;
use Doctrine\ORM\Tools\Console\ConsoleRunner;

// replace with file to your own project bootstrap
/** @var Illuminate\Foundation\Application $app */
$app = require_once __DIR__ . '/bootstrap/app.php';

/** @var Illuminate\Contracts\Console\Kernel $kernel */
$kernel = $app->make('Illuminate\Contracts\Console\Kernel');
$kernel->bootstrap();

$app->boot();

// replace with mechanism to retrieve EntityManager in your app
$entityManager = $app[EntityManager::class];

return ConsoleRunner::createHelperSet($entityManager);

Note you will need to have already registered the EntityManager with your app through a service provider. You can use a package like mitchellvanw/laravel-doctrine or opensolutions/doctrine2bridge-l5 to setup Doctrine in Laravel 5.

Little hack to support multiple read-only slaves in Laravel. There really should be native support for multiple slaves.