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

Running the first build


This is the moment of truth. In the past 30 pages, we installed and configured many packages and libraries to see this moment. To see how Jenkins works, click on the Build Now button and watch the build process in action:

You can always click on the build link at any time and watch the process live by choosing Console Output:

As you can see, the project build has no errors and if you go back to the Jenkins dashboard, you will see the blue success icon that indicates our first build has completed successfully:

It is likely to face a couple of errors before working successfully. As you can see, we have a long list of different things to set up. So a misspelled name or wrong path is not unusual. What I encourage you to do is read the error message carefully, go to the line number in the build.xml file, and see how you can fix it.

Sometimes, you may need to work around it. You might copy executable files to your /usr/local/bin folder and change the XML file accordingly. I...