Marcel Djaman mdjaman

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 \

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!

\

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

	wget http://download.gna.org/wkhtmltopdf/0.12/0.12.2.1/wkhtmltox-0.12.2.1_linux-trusty-amd64.deb
	sudo apt-get update
	sudo apt-get install wkhtmltox
	sudo apt-get -f install
	sudo dpkg -i wkhtmltox-0.12.2.1_linux-trusty-amd64.deb
	wkhtmltopdf -V
	rm wkhtmltox-0.12.2.1_linux-trusty-amd64.deb

	#!/usr/bin/env bash

	_UVERSION=${1:-precise}
	_WVERSION=0.12.2.1
	_WVERSION_M=`echo $_WVERSION \| awk -F. '{print $1"."$2}'`

	FILENAME="wkhtmltox-${_WVERSION}_linux-${_UVERSION}-amd64.deb"
	URL="http://download.gna.org/wkhtmltopdf/${_WVERSION_M}/${_WVERSION}/${FILENAME}"

	apt-get update

	#!/bin/sh

	# PATH TO YOUR HOSTS FILE
	ETC_HOSTS=/etc/hosts

	# DEFAULT IP FOR HOSTNAME
	IP="127.0.0.1"

	# Hostname to add/remove.
	HOSTNAME=$1

	#!/bin/bash
	# This script is used for create virtual hosts on CentOs.
	# Created by alexnogard from http://alexnogard.com
	# Improved by mattmezza from http://you.canmakethat.com
	# Feel free to modify it
	# PARAMETERS
	#
	# $usr - User
	# $dir - directory of web files
	# $servn - webserver address without www.

	var express = require('express'),
	app = express(),
	cookieParser = require('cookie-parser'),
	session = require('express-session'),
	RedisStore = require('connect-redis')(session);

	app.use(express.static(__dirname + '/public'));
	app.use(function(req, res, next) {
	if (~req.url.indexOf('favicon'))
	return res.send(404);

	// include the AMQPlib Classes \|\| use an autoloader

	// queue/exchange names
	$queueRightNow = 'right.now.queue';
	$exchangeRightNow = 'right.now.exchange';
	$queueDelayed5sec = 'delayed.five.seconds.queue';
	$exchangeDelayed5sec = 'delayed.five.seconds.exchange';

	$delay = 5; // delay in seconds

	App configuration in environment variables: for and against

	For (some of these as per the 12 factor principles)

	1) they are are easy to change between deploys without changing any code

	2) unlike config files, there is little chance of them being checked
	into the code repo accidentally

	3) unlike custom config files, or other config mechanisms such as Java