News Feed
Sections




News Archive
feed this:

Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Symfony Blog:
Thelia, a Symfony-based e-commerce solution
September 17, 2014 @ 11:16:48

On the Symfony blog today they've posted an interview with Manuel Raynaud, the lead developer on the Thelia project. Thelia is a Symfony-based e-commerce solution that is free to download and use (and can easily be installed via Composer).

An interview with Manuel Raynaud, lead developer of Thelia, a Symfony-based e-commerce solution. Introducing the new Thelia 2 and how it's in perfect harmony with Symfony.

The interview starts with a brief introduction of Manuel and a quick overview of what the Thelia project is about and the current state of things. They get into some of the story behind Thelia and what parts of Symfony (components) it uses behind the scenes. They finish out the interview talking about some of the advantages the project offers and challenges they've faced along the way. There's also a bit about how Thelia is involved in the Symfony events and community.

0 comments voice your opinion now!
interview community symfony thelia ecommerce manuelraynaud

Link: http://symfony.com/blog/thelia-a-symfony-based-e-commerce-solution

Marc Morera:
Bye Bye Symfony
September 04, 2014 @ 12:41:00

In his most recent post Marc Morera says bye bye to Symfony and "hello to PHP". Confused? His point is that using the Symfony components as a whole in the framework isn't the only option anymore. You can use them just as effectively as pieces of a larger PHP project, puling them in as needed.

The reason of this post is just to tell you, with a simple example, how to say Bye Bye, Symfony! and say Hi PHP!. This really means uncouple from Symfony Components and still use them as the default implementation, while we can securely remove, from the composer require block, our Symfony dependencies.

He starts off with a simple example showing how to use Symfony's "UrlGeneratorInterface" to create a URL output class that can be injected to use in the route handling of the application. He then moves on to a more real-life example (a metaphor) using a USB connection and the adapters/cables that could be involved to connect various devices. He then shifts back over to the world of code and describes a specification interface that can be used with the URL generation and remove the Symfony dependency from it. On top of this he builds an adapter object that brings the Symfony component back into the picture and abstracts it out a level to make for more flexibility and testability in the long run.

We win maximum implementation flexibility and minimum coupling. Would be wise to say that a PHP project should tend to this thought, but once again, it depends on many factors. [...] Using ports and adapters is really a great tool for those who want to uncouple from implementations and a great pattern if you develop open source. Open source should satisfy as people as possible, so remember, specify and then implement.
0 comments voice your opinion now!
symfony component abstract tutorial interface specification

Link: http://mmoreram.com/blog/2014/09/01/bye-bye-symfony/

Matthias Noback:
Decoupling your (event) system
August 26, 2014 @ 11:15:17

Matthias Noback has continued his look at event handling in PHP applications (well, Symfony-related ones at least) in his latest post. In this latest post he focuses more on abstracting out the event handling process and decoupling it from your application as much as possible.

You are creating a nice reusable package. Inside the package you want to use events to allow others to hook into your own code. You look at several event managers that are available. [...] Introducing this dependency is not without any problem: everybody who uses my/package in their project will also pull in the [event dispatcher] package, meaning they will now have yet another event dispatcher available in their project (a Laravel one, a Doctrine one, a Symfony one, etc.). This doesn't make sense, especially because event dispatchers all do (or can do) more or less the same thing.

As mentioned, he focuses in on the Symfony ecosystem and the event handlers commonly used there. He talks about some of the disadvantages of the Symfony EventDispatcher and how its interface can lead to code bloat due to it's verbosity (flexibility?). He talks about its violations of the Interface Segregation Principle and how he would structure the listener setup and handling if he was starting from scratch. To this end, he's created an adapter that wraps around an EventDispatcher interface and works with objects for the different kinds of events rather than the string names.

0 comments voice your opinion now!
decouple event manager dispatch handling symfony adapter object

Link: http://php-and-symfony.matthiasnoback.nl/2014/08/symfony2-decoupling-your-event-system/

Geshan Manandhar:
3 Bundles to get started with REST in Symfony 2 and some tips
August 13, 2014 @ 12:18:05

Geshan Manandhar has a recent post that shares three Symfony bundles that can help you out greatly when creating RESTful applications and APIs. Links and a summary of each bundle are provided.

"I found out that you guys just build an amazing mobile app for your e-commerce venture, I heard you are using Symfony 2 for your back-end APIs. How did you make it that fast?" This is not very different that what I was asked some months back. The answer is we use a Service Oriented Architecture (SOA) where all back-end service follow the REST architecture to communicate with all the clients. The client can be built in any language as longs a they can do HTTP calls. Lets look at what Symfony 2 bundles you can use to build a similar scalable, fast and cacheable REST APIs.

His suggested bundles (all available to be installed via Composer) are:

The first two help more with the overall API structure and handling while the last (Lexi) is an effective way for handling authentication for the requests to your application.

0 comments voice your opinion now!
symfony bundles rest api top3 list

Link: http://geshan.blogspot.ae/2014/07/3-bundles-to-get-started-with-rest-in.html

Symfony Blog:
Pre-conference workshops at SymfonyLive New York and SymfonyCon Madrid are online!
August 13, 2014 @ 10:22:55

On the Symfony blog today they've officially announced the workshops that will be happening at this year's SymfonyCon Madrid and Symfony Live New York.

About 3 weeks ago, we launched 2 different polls to ask you what workshops you wanted to attend before SymfonyLive New York and SymfonyCon Madrid. First, we want to thank all the people who participated in the poll, so many of you answered, thank you very much for your time! Thanks to your votes, we were able to know which workshops were really interesting for you.

At Symfony Live New York you'll be able to attend Fabien's "Symfony Best Practices" or "Building RESTful Applications with Symfony" (the top two most requested training sessions). At SymfonyCon Madrid there's even more choices:

  • Building RESTful Applications with Symfony
  • Symfony Best Practices
  • Deploying Symfony Applications
  • Profiling PHP Applications

You can find out more about these two conferences from their main event websites: Symfony Live New York and SymfonyCon Madrid.

0 comments voice your opinion now!
symfony symfonycon symfonylive madrid newyork workshop list

Link: http://symfony.com/blog/pre-conference-workshops-at-symfonylive-new-york-and-symfonycon-madrid-are-online

Reddit.com:
PHP library authors Have you considered to arrange security bug bounties?
August 06, 2014 @ 10:39:00

In this new post to Reddit.com Timoh suggests something that could definitely help improve the overall security of the PHP ecosystem - a bug bounty system, providing libraries and projects an easy way to security-related submissions for their code.

To encourage software security research on the open-source PHP libraries we use everyday, I have been brainstorming the possibilities for us, the code authors, to start to offer security bug bounties on the projects we maintain. It is a shame such a few PHP projects encourages security research by offering bug bounties, and I think it doesn't have to be this way.

He describes his ideas for the system including the ability to offer both monetary bounties and other kinds of recognition as well. Comments on the post are largely supportive, agreeing with him that it can definitely help things. He also makes the suggestion of getting frameworks with corporate backings (like Zend Framework and Symfony) to be some of the leaders and be an example to other projects and get them on board. What do you think? Add your own thoughts and suggestions about the project to the mix!

0 comments voice your opinion now!
bugbounty service project library zendframework symfony bounty recognition

Link: http://www.reddit.com/r/PHP/comments/2cpu6v/php_library_authors_have_you_considered_to/

Symfony Blog:
Push it to the limits - Symfony2 for High Performance needs
August 04, 2014 @ 13:51:48

On the Symfony blog today they've posted a use case that talks about Symfony meeting some high performance needs and some of the development that was done to make it happen.

For most people, using full-stack frameworks equals slowing down websites. At Octivi, we think that it depends on correctly choosing the right tools for specific projects. When we were asked to optimize a website for one of our clients, we analyzed their setup from the ground up. The result: migrate them toward Service Oriented Architecture and extract their core-business system as a separate service. In this Case Study, we'll reveal some architecture details of 1 Billion Symfony2 Application. We'll show you the project big-picture then focus on features we really like in Symfony2. Don't worry; we'll also talk about the things that we don't really use.

They start with some of the business requirements they needed to meet and how it influenced the overall architecture of the application. They cover some of the things they liked the most about using the framework including bundles and using the EventDispatcher component. Some example code is also included for the custom handling they created for routing, CLI commands and request handling. There's also a mention of using the Profiler, Stopwatch and Monolog trio to do some performance analysis on the resulting application. Finally, there's a brief mention of some of the tools they're not using and why (two of them): Doctrine and Twig.

0 comments voice your opinion now!
symfony usecase performance need application custom

Link: http://symfony.com/blog/push-it-to-the-limits-symfony2-for-high-performance-needs

Symfony Blog:
Improving REST in Symfony
July 11, 2014 @ 12:15:56

On the Symfony blog there's a recent post about a new effort being started to help improve REST in Symfony-based applications. William Durand talks about some of the current tools and some of the missing features/difficulties each has. This effort wants to help change that.

Building APIs with Symfony is not new. We've done that since the early beginning of Symfony: Askeet, Jobeet, it's been a long time! Nowadays, more and more web applications are made of an API and a client side application. Sharing data across applications using APIs also became an essential feature. [...] For most of us, it is not as clear as it should be, and we can certainly do better than what we have right now! Hence the creation of a working group to gather both people and knowledge for REST in Symfony: https://groups.google.com/forum/#!forum/resting-with-symfony.

The target of the group is just about anyone associated with the development of APIs: developers who build them, developers to contribute to Symfony's REST functionality, people with questions about REST and, really, anyone else interested. It's a part of their wider developer experience initiative they've recently ramped up.

0 comments voice your opinion now!
developer experience rest discussion group symfony framework

Link: http://symfony.com/blog/improving-rest-in-symfony

Symfony Blog:
First Online Symfony Community Hack Day July 5th!
July 01, 2014 @ 11:58:07

On the Symfony blog today Ryan Weaver has posted a note about the first ever Symfony online community hack day coming up on July the 5th.

Last week, I talked about the Symfony Experience, and announced a new Developer Experience Initiative. [...] And now it's time to put our ideas into action, with the first community hack day on July 5th. This hack day is for everyone and we'll focus on tasks from all around the Symfony world: the core code and third party bundles. This is our chance to really push on things that never quite get done as well as they could: third party bundle documentation, exception messages, shortcuts, etc.

The event will be happening on July 5th from 9am to 8pm Central European Time (3am to 2pm Eastern time in the US) and will be run from the #symfony channel on the Freenode IRC network. There'll be plenty to do, so if you're interested in getting involved, reach out to Ryan or Javier once you're on and they can point you in the right direction. More information can be found on the Symfony blog.

0 comments voice your opinion now!
symfony blog community hackday july2014 developer experience

Link: http://symfony.com/blog/first-online-symfony-community-hack-day-july-5th

Matthias Noback:
Symfony2 Framework independent controllers parts 2 & 3
June 19, 2014 @ 09:45:34

Matthias Noback has posted the next two parts of his "framework independent controllers" series (it started here) looking at avoiding annotations and tying up some loose ends.

From part two about annotations:

In the previous part of this series we decreased coupling of a Symfony controller to the Symfony2 framework by removing its dependency on the standard Controller class from the FrameworkBundle. Now we take a look at annotations. They were initially introduced for rapid development (no need to create/modify some configuration file, just solve the issues inline!) [...] This might not seem such a big problem at all, but the SensioFrameworkExtraBundle is a bundle, which means it only works in the context of a Symfony2 application. We don't want our controller to be coupled like this to the framework (at least, that is the point of this series!), so we need to remove the dependency.

He shows how to decouple this functionality through a proper routing configuration, fetching the needed data yourself for the request and generating the request object yourself. In part three he covers some of the comments already made about the series and how to take the final steps to abstracting out the controllers: removing bundle names from templates, removing the HttpFoundation dependency and letting go of "action methods".

0 comments voice your opinion now!
controller independent symfony series part2 part3

Link: http://php-and-symfony.matthiasnoback.nl/tags/controller/


Community Events





Don't see your event here?
Let us know!


framework introduction laravel tips deployment community api list zendserver podcast conference series threedevsandamaybe symfony development interview language release bugfix code

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework