Jean-Marie Lamodière JMLamodiere

Debug your PHP in Docker with Intellij/PHPStorm and Xdebug

For your local dev, create a Dockerfile that is based on your production image and simply install xdebug into it. Exemple:

FROM php:5

RUN yes | pecl install xdebug \
&amp;&amp; echo "zend_extension=$(find /usr/local/lib/php/extensions/ -name xdebug.so)" &gt; /usr/local/etc/php/conf.d/xdebug.ini \

From Symfony 2.3 to Symfony 2.7: the complete guide

Objectives

assume your code doesn't use any deprecated from versions below Symfony 2.3
update dependencies from 2.3 to 2.7
do not support "deprecated", be "Symfony3-ready"
list tasks component by component, bundle by bundle.

DDD, CQRS and Event Sourcing in PHP

Broadway - Infrastructure and testing helpers for creating CQRS and event sourced applications
EventCentric.Core - Event Sourcing and CQRS in PHP
LiteCQRS - Small convention based CQRS library for PHP
predaddy - Common DDD classes including an annotation driven message bus and tools for CQRS and Event Sourcing
ProophEventSourcing - Provides basic functionality for event-sourced aggregates
ProophEventStore - PHP 5.4+ EventStore Implementation
ProophServiceBus - PHP Enterprise Service Bus Implementation supporting CQRS and DDD

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

	/*
	https://scalafiddle.io/sf/sniohcZ/3
	(old version: https://scalafiddle.io/sf/sniohcZ/1)

	Use PassThroughFlow when you have a message that should be used in a
	flow that trasform it but you want to maintain the original message for
	another following flow.
	For example if you consume messages from Kafka (CommittableMessage).
	You process the message (transform, save it inside a database, ...) and then you need again the original message
	to commit the offset.

	#!/bin/bash

	add()
	{
	sed -i '1 s/<?php/<?php\
	declare(strict_types=1);/g' $1

	}

	# [Git]
	_completion_loader git
	alias g="git"
	__git_complete g _git
	alias ga="git add"
	__git_complete ga _git_add
	alias gap="git add --patch"
	__git_complete gap _git_add
	alias gb="git branch"
	__git_complete gb _git_branch

	#!/bin/bash

	# remove exited containers:
	docker ps --filter status=dead --filter status=exited -aq \| xargs -r docker rm -v

	# remove unused images:
	docker images --no-trunc \| grep '<none>' \| awk '{ print $3 }' \| xargs -r docker rmi

	# remove unused volumes:
	find '/var/lib/docker/volumes/' -mindepth 1 -maxdepth 1 -type d \| grep -vFf <(

	<?php

	/**
	* Filtering a array by its keys using a callback.
	*
	* @param $array array The array to filter
	* @param $callback Callback The filter callback, that will get the key as first argument.
	*
	* @return array The remaining key => value combinations from $array.
	*/