use Illuminate\Database\Query\Builder;
use Illuminate\Database\Query\Expression
Builder::macro('joinLateral', function ($query, $as, $type = 'inner') {
[$query, $bindings] = $this->createSub($query);
tail -f -n 450 storage/logs/laravel*.log \ | |
| grep -i -E \ | |
"^\[\d{4}\-\d{2}\-\d{2} \d{2}:\d{2}:\d{2}\]|Next [\w\W]+?\:" \ | |
--color |
<?php | |
if (!function_exists('interface_exists')) { | |
die('PHP version too old'); | |
} | |
$throwables = listThrowableClasses(); | |
$throwablesPerParent = splitInParents($throwables); | |
printTree($throwablesPerParent); | |
if (count($throwablesPerParent) !== 0) { | |
die('ERROR!!!'); |
It's time someone compiled a list of nationalities to use within a web application. This gist attempts to make a first move at that.
I've also compiled a list of countries
<?php | |
/** | |
* Join a string with a natural language conjunction at the end. | |
*/ | |
function natural_language_join(array $list, $conjunction = 'and') { | |
$last = array_pop($list); | |
if ($list) { | |
return implode(', ', $list) . ' ' . $conjunction . ' ' . $last; | |
} | |
return $last; |
<?php | |
namespace Tests; | |
use Mail; | |
use Swift_Message; | |
use Swift_Events_EventListener; | |
trait MailTracking | |
{ | |
/** | |
* Delivered emails. |
{"lastUpload":"2019-07-27T19:36:28.740Z","extensionVersion":"v3.4.1"} |
<?php | |
namespace Deployer; | |
require 'recipe/common.php'; | |
// Project name | |
set('application', 'enovate.co.uk'); | |
// Project repository | |
set('repository', 'git@githosting.com:enovatedesign/project.git'); |
I recently had the need to write a small url shortening application. I am aware that this problem has been solved quite a few times before, but what is being a developer if not reinventing the wheel just for the heck of it? Custom CMS anyone?
Knowing that this was going to be a tiny RESTful API and also knowing that Laravel 5.2 had API rate limiting built in, I was eager to give it a try. Taylor Otwell being Taylor Otwell shipped 5.2 with the rate limiting defaults set up out of the box and I had my application building out short url's in a matter of minutes. The problem for me came when I wanted to start associating those short urls with a user.
Typically my applications have a UI and authentication is done through a simple login page. Obviously for a RESTful API, having a login page isn't ideal. Instead, my hope was to have users append an api_token
to the end of their query string and use that to auth