morozow

Инструмент автоматизации управления версиями

Версионирование

Версионирование — разработка и управление несколькими выпусками продукта, которые имеют тот же общий функционал, но усовершенствованы, модернизированы либо индивидуализированы. Коротко, версия говорит об изменении продукта. Как версия говорит об изменении продукта? Давайте назовем систему упорядочивания символов для обозначения версии продукта — схемой версионирования. Различные схемы версионирования были созданы для отслеживания версий различного программного обеспечения.

Semantic Versioning: Major.Minor.Patch

Схем версионирования много, но мы сталкиваемся с Семантическим версионированием (Semantic Versioning) каждый день. Для Семантического версионирования характерно то, что номера версий и то, как они меняются, передают смысл содержания исходного кода и какие модификации были применены от одной версии к другой. Рассмотрим, каким образом формируется номер Семантической версии.

Patch version, обратно совместимые исправления: n.n.X

swalkinshaw

Moved to Shopify/graphql-design-tutorial

DragonBe

PHP conferences 2016

Name	Location	Start Date	End Date	Attending	Speaking
SkiPHP 2016	Salt Lake City, USA	01-14	01-15
PHPBenelux Conference 2016	Antwerp, Belgium	01-29	01-30	X
SunshinePHP 2016	Miami, USA	02-04	02-06	X	X
PHP UK Conference 2016	London, UK	02-18	02-19
Midwest PHP Conference 2016	Minneapolis, USA	03-04	03-05
LoneStarPHP 2016	Dallas, USA	04-07	04-09

tjamps

Basic RESTful API with Symfony 2 + 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 authentication
• 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 2 framework. The following SF2 bundles are used :

morozow

<?php

/**
 * This recurcive function build full path for nested set node by classic array
 *
 * @param $tree
 * @param $needle
 * @param array $path
 * @return array|bool
 */

lologhi

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. :

toranb

module.exports = function(grunt) {
  grunt.loadNpmTasks('grunt-contrib-watch');
  grunt.loadNpmTasks('grunt-contrib-concat');
  grunt.loadNpmTasks('grunt-ember-template-compiler');
  grunt.loadNpmTasks('grunt-hashres');

  grunt.initConfig({
    watch: {
      scripts: {
        files: ['foo/static/something_ui/js/app/*.js', 'foo/static/something_ui/templates/*.handlebars'],

danvbe

I have managed to install this… and make it work. I implemented it for Facebook and Google, but you can extend it. My solution it is mostly as described in #116, with a bit of more code presented. The key aspects that lack in the #116 presentation (IMO) are:

• the registration as service of your custom FOSUBUserProvider (with the necessary parameters)
• set the service for oauth_user_provider in the security.yml with your custom created service

Here are the steps:

1. Routing. In routing.yml I have added all the routes for both bundles.
2. Configuration. I have set the config.yml mostly as it is presented in the HWIOAuthBundle.
3. Security. I have set the security.yml mostly as it is presented in the HWIOAuthBundle (though my routes are using /login pattern, not /connect). Also, the oauth_user_provider is set for my custom service.

tawfekov

<?php
include '../vendor/autoload.php';
$classLoader = new \Doctrine\Common\ClassLoader('Entities', __DIR__);
$classLoader->register();

$classLoader = new \Doctrine\Common\ClassLoader('Proxies', __DIR__);
$classLoader->register();

// config
$config = new \Doctrine\ORM\Configuration();