|
You are here |
williamdurand.fr | ||
| | | | |
tomasvotruba.com
|
|
| | | | | Series about PHP CLI Apps continues with 3rd part about writing Symfony Console Application with Dependency Injection in the first place. Not last, not second, **but the first**. Luckily, is easy to start using it and very difficult to | |
| | | | |
php-and-symfony.matthiasnoback.nl
|
|
| | | | | [AI summary] A detailed technical tutorial on creating and configuring custom UserProviders in Symfony2 using YAML for authentication | |
| | | | |
richardmiller.co.uk
|
|
| | | | | Background I am recreating Lime Thinking's current website [http://www.limethinking.co.uk] using Symfony2 [http://symfony.com/], much of the site is made up of what are effectively static pages. The main content of the page is stored as an XML file which then has the overall XSL template | |
| | | | |
blog.theamazingrando.com
|
|
| | | The point of this post isn't to convince you of the usefulness of Dependency Injection there's been plenty of pixels spilled about it already. Instead, I want to talk about using Dry::Container to alleviate some of the pain points that DI introduces. | ||