The world for developers is becoming more and more agile. This increases the importance of having a great deploy process. Being able to adapt and react fast to changes is the way to stay agile. With a slow or complicated deploy process it becomes impossible to stay agile. You want to be able to respond fast to feedback and iterate with a fast and easy deploy (or rollback). That is the agile way.

A deploy is an important part of the software  development process. Somehow it has been forgotten a bit in the PHP community. I hope to share my thoughts and experiences in this book to aid you in optimizing your deploy process. "Software rot" is something that happens to code if it's not maintained in a proper way. When it comes to deploy I call it "shipping rot". Let's try to stay away from that and treat our deploy process as any other important part of our applications.

You might be a developer. You might be the manager of or product owner to a team of developers. You will benefit from this whomever you might be. Whether you want to optimize the deploy process for technical or management reasons doesn't matter. 

The style of the book will not be in the form of that you need to read the entire thing from start to finish. You could pick the areas where your process is suffering and focus on that. There will be both theory and technical implementation of the concepts.

This book is fully open source, you can find everything in the github repository: https://github.com/modess/deploying-php-applications, the book also has an external landing page here: http://www.deployingphpapplications.com/

It happens so unexpectedly: your project started off great at first with you developing at a rapid pace, but before you know it, you've come to a screeching halt. Adding the simplest of features takes forever. Unrelated pieces of code keep breaking without being touched. You've given up on tests because you simply don't have time and, frankly, they're all broke at this point anyway.

Your code doesn't have to be an unwieldy, soul crushing nightmare that revokes any joy of programming you once had.

Finding the best way to organize your code is one of the hardest parts of coding. 

Determing the best way to architect your application is a very important step in development. Heading in the wrong direction can lead to a nightmare later, and make it nearly impossible to refactor the application to meet new demands, and can make properly testing the application a pain. While the methods outlined in this book aren't the only way to go about developing an application, they do provide a framework for developing applications that are:

• Testable
• Refactorable
• Easy to work with
• Easy to maintain

In this book, we cover the Clean Architecture, coined by Uncle Bob, and how to implement it in PHP, as well as the concepts of SOLID design, various design patterns, and a look at various architectures.