Angel Psiakis mapsi

If someone asked me the question "what layout should I use for my Go code repository?", I'd start by asking back "what are you building: an executable, or a library?"

Single executable

Stage 1: single source file

Create a directory named however you want your final executable to be called (e.g. "mycommand"), change into that directory, and create the following files:

	version: '2'
	services:
	php:
	image: php:5.6-fpm-alpine
	volumes:
	- data:/_data
	- ./site:/var/www/html:ro
	networks:
	- backend
	command: sh -c 'chown www-data /_data && exec php-fpm'

	APP_ENV=testing
	APP_KEY=base64:DimZ0aVNA8ZWtWxTB4fDxFc6lL1wM2C7evETA4QK3+c=
	APP_DEBUG=true
	APP_LOG_LEVEL=debug
	APP_URL=http://localhost:8081

	DB_CONNECTION=mysql
	DB_HOST=mysql
	DB_PORT=3306
	DB_DATABASE=secca_testing

	<?php

	abstract class AbstractEntity extends AbstractValueObject
	{
	/**
	* Offset Set
	*
	* @param mixed $offset
	* @param mixed $value
	*