sudo add-apt-repository ppa:gnome-terminator
sudo apt-get update
sudo apt-get install terminator
Terminator should be setup as default now. Restart your terminal (shortcut: "Ctrl+Alt+T").
<?php | |
// composer require fabpot/goutte | |
Route::get('docs', function(){ | |
$host = 'http://laravel.com'; | |
$base = '/docs/5.1/'; | |
$client = new Goutte\Client(); | |
$crawler = $client->request('GET', $host.$base); |
Dear members of the development team, CU a few days ago I commented the announcement, that Neos and Flow get rid of "TYPO3" as part of their names, as follows:
Removing "TYPO3" from Neos and Flow makes it easier to quietly abandon these products. \o/
Additionally to this tweet I had a small twitter conversation resulting in this tweet:
<?php | |
namespace FixtureLoader; | |
use Doctrine\Common\Persistence\Mapping\ClassMetadata; | |
use Doctrine\Common\Persistence\ObjectManager; | |
use Doctrine\Instantiator\Instantiator; | |
class SimpleFixtureLoader | |
{ |
<?php | |
class FastForwarder | |
{ | |
protected $skipWhen = []; | |
protected $numDays = 0; | |
public static function createWithDays($num_days) | |
{ | |
$ff = new static; |
<?php | |
/** | |
* ProcessWire 'Hello world' demonstration module | |
* | |
* Demonstrates the Module interface and how to add hooks. | |
* | |
* See README file for further links regarding module development. | |
* | |
* ProcessWire 2.x |
<?php | |
use PHPUnit_Framework_TestCase; | |
use Symfony\Component\DomCrawler\Crawler; | |
class SimpleHttpTest extends PHPUnit_Framework_TestCase | |
{ | |
public function testHttp() | |
{ | |
$crawler = new Crawler(file_get_contents('http://myapp.lcl/hello/Jon')); |
#!/usr/bin/env bash | |
d=$(date +%s) | |
remote='some-aws-box' | |
dir="composer-$d.tmp" | |
if [ -f composer.json ]; then | |
ssh $remote mkdir "$dir" | |
scp composer.json $remote:"$dir"/composer.json |
Are you making use of the event handling system like Symfony event handler, Aura.Signal, Zend event manager or any other in your core framework?
Are you using signal/events before they hit the action class ( controller action ) ?
I have a feeling it will be good to have an event handling system in core of a framework.
The basic idea is to call a signal