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

On the CI side of the story


Last time, as you pushed the changes to your GitHub repository, you probably received a couple of e-mails informing you about the success or failure of the new build. You can celebrate if your build is successful. However, if it is not, don't panic and just follow this two-step process.

First, make sure that all unit tests and functional tests in your local machine pass successfully. If there is something wrong here, you should not expect a successful build from your Jenkins instance on EC2. For those who created or modified the tests and codes themselves, it could be a simple misspelling error or some serious logical issue. Spot the problem using log messages and fix it. Then try again.

For those who cloned the code from my GitHub repository, it could be a local configuration issue. If you branched out your working Git repository, make sure that you are on the right branch. If something needed to be merged, check out to your Dev branch first and then do it. Check...