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

Creating a new job in Jenkins


At this stage, the setup and configuration part is over and we are ready to create our first CI job:

  1. Log in to your Jenkins application and click on New Item in the left navigation bar. Then, choose a name for the job, select Build a free-style software project, and press OK:

  2. Under the Source Code Management section, choose Git and add the mava project repository here (The mava project is located at [email protected]:Soolan/mava.git; you are welcome to fork this project to your local repository or create a new repository and push your own Symfony project here.):

  3. As you can see, because of the lack of credentials, an error message is shown. To fix the problem, we need to add the Jenkins credentials to our mava GitHub repository. In the EC2 instance terminal, log in as Jenkins:

    $ sudo su – jenkins
    
  4. Now, generate public/private key pairs:

    $ ssh-keygen -t dsa
    
    Generating public/private dsa key pair.
    Enter file in which to save the key (/var/lib/jenkins/.ssh/id_dsa): 
    Enter...