Vladimir L vladimir-light

Basic RESTful API with Symfony 3 + FOSRestBundle (JSON format only) + FOSUserBundle + FOSOauthServerBundle

The API we are creating in this gist will follow these rules :

The API only returns JSON responses
All API routes require authenticationu
Authentication is handled via OAuth2 with password Grant Type only (no need for Authorization pages and such).
API versioning is managed via a subdomain (e.g. v1.api.example.com)

The API will be written in PHP with the Symfony 3 framework. The following SF2 bundles are used :

The Problem

In Javascript this is bound in unexpected ways. Functions, in particular, create a new 'this' and so when you want to keep a reference to an "outer" object you sometimes see the pattern:

var self = this;

as in:

var self = this;

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 \

What's the difference between cascade="remove" and orphanRemoval=true in Doctrine 2

TLDR: The cascade={"remove"} is like a "software" onDelete="CASCADE", and will remove objects from the database only when an explicit call to $em->remove() occurs. Thus, it could result in more than one object being deleted. orphanRemoval can remove objects from the database even if there was no explicit call to ->remove().

I answered this question a few times to different people so I will try to sum things up in this Gist.

Let's take two entities A and B as an example. I will use a OneToOne relationship in this example but it works exactly the same with OneToMany relationships.

class A

It's still a work in progress...

Intro

As William Durand was recently explaining in his SOS, he "didn't see any other interesting blog post about REST with Symfony recently unfortunately". After spending some long hours to implement an API strongly secured with oAuth, I thought it was time for me to purpose my simple explanation of how to do it.

Ok, you know the bundles

You might have already seen some good explanation of how to easily create a REST API with Symfony2. There are famous really good bundles a.k.a. :

	FROM ubuntu:16.04

	RUN apt-get -y update && apt-get install -y php7.0-fpm php7.0-cli php7.0-curl php7.0-gd php7.0-intl php7.0-zip php7.0-pgsql build-essential git gcc make re2c libpcre3-dev php7.0-dev curl

	RUN curl -sS http://getcomposer.org/installer \| php
	RUN mv composer.phar /usr/local/bin/composer

	RUN composer global require "phalcon/zephir:dev-master"

	RUN mkdir -p /opt/www

	<?php
	class MyRepository extends EntityRepository
	{
	public function whereInSubQuery(User $user)
	{
	$queryBuilder = $this->createQueryBuilder('my_repository');

	$queryBuilder
	->where(
	$queryBuilder->expr()->in(

	/*
	Update the SSLVERSION for CURL to support PayPal Express moving to TLS 1.2

	More info: https://devblog.paypal.com/upcoming-security-changes-notice/

	Your server will need to be updated to a supported version of OpenSSL for this to work.

	Add this code to your active theme's functions.php or a custom plugin.
	*/
	function my_http_api_curl($handle) {

	#!/bin/bash

	target_branch="production"
	working_tree="PATH_TO_DEPLOY"

	while read oldrev newrev refname
	do
	branch=$(git rev-parse --symbolic --abbrev-ref $refname)
	if [ -n "$branch" ] && [ "$target_branch" == "$branch" ]; then

	# For a symfony application to work properly, you MUST store this .htaccess in
	# the same directory as your front controller, index.php, in a standard symfony
	# web application is under the "public" project subdirectory.

	# Use the front controller as index file.
	DirectoryIndex index.php

	# Uncomment the following line if you install assets as symlinks or if you
	# experience problems related to symlinks when compiling LESS/Sass/CoffeScript.
	# Options +FollowSymlinks