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

Simple Email Service


Amazon Simple Email Service (SES) is an SMTP server to send limited amounts of e-mails per day. At the time of writing this book, it is about 200 e-mails per day, which is more than enough. To set up SES, follow these steps:

  1. On the console page, click on SES under App Services:

  2. On the next page, click on SMTP Settings, and copy the server name and port number to a file as you will need them for the next step:

  3. Click on the Create My SMTP Credentials button and wait until you are redirected to the IAM service (another Amazon service to manage credentials). Click on the Create button:

  4. Copy and paste the username and password fields in the following page because you will need them for the next topic as well:

    Note

    The credentials provided here are fake. Don't use them. Use your custom ones. You don't think I'm going to expose my password to the world, do you?

Configuring Jenkins

Now that we have the mail server and Jenkins plugins in place, it is time to configure Jenkins itself...