Book Image

Mastering Symfony

Book Image

Mastering Symfony

Overview of this book

In this book, you will learn some lesser known aspects of development with Symfony, and you will see how to use Symfony as a framework to create reliable and effective applications. You might have developed some impressive PHP libraries in other projects, but what is the point when your library is tied to one particular project? With Symfony, you can turn your code into a service and reuse it in other projects. This book starts with Symfony concepts such as bundles, routing, twig, doctrine, and more, taking you through the request/response life cycle. You will then proceed to set up development, test, and deployment environments in AWS. Then you will create reliable projects using Behat and Mink, and design business logic, cover authentication, and authorization steps in a security checking process. You will be walked through concepts such as DependencyInjection, service containers, and services, and go through steps to create customized commands for Symfony's console. Finally, the book covers performance optimization and the use of Varnish and Memcached in our project, and you are treated with the creation of database agnostic bundles and best practices.
Table of Contents (17 chapters)
Mastering Symfony
Credits
About the Author
About the Reviewers
Index

How assets are organized


When you look at bundles in Symfony, you might think this is one big mess. How can you possibly get things working while there are so many Resources/ folders all over the place and each of them contains a set of templates, .css, and .js files?

Here is the situation: there are some assets that belong to the bundles created by us. There are other assets that came with a vendor when we installed a third-party bundle, and finally there are some assets that belong to the project globally and cannot be saved in any specific bundle. The question is how to organize them.

Have a look in the web/ directory and you will find the answer. As you can see, all resources that have been used so far in this project are sitting there. So, technically, Symfony does not need to look in each bundle individually to find an image, for example. Actually, this is the best way to do it. If you decide to use a bundle somewhere else, you just install it there and you don't need to look for its...