Deploying PHP Applications
Deploying PHP Applications
About the Book
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/
About the Author
Bundles that include this book
About the Contributors
Proof reader
Table of Contents
-
Introduction
- Background
- Who it’s for
- Outside its scope
- Assumptions
- About the author
- Code samples
- Thanks to
-
1. Automate, automate, automate
- 1.1 One button to rule them all
- 1.2 Example of a manual step
- 1.3 Time is always a factor
-
2. Goals
- 2.1 How it generally begins
- 2.2 Maturity
- 2.3 Agility
- 2.4 Plan for a marathon
- 2.5 Release cycles
- 2.6 Technical debt and rot
- 2.7 The list
-
3. Environments
- 3.1 Repeatable
- 3.2 Configuration / environment variables
- 3.3 Local environment
- 3.4 Development environment
- 3.5 Staging environment
- 3.6 Production environment
- 3.7 Testing environment(s)
- 3.8 Simplify server access
-
4. Atomic deploys
- 4.1 What is atomicity?
- 4.2 Achieving atomicity
- 4.3 Concept of builds
- 4.4 File persisted data (shared data)
- 4.5 Symbolic folder links
- 4.6 Proposed folder structure
- 4.7 Pseudo deploy process
-
5. Tools
- 5.1 Deployer
- 5.2 Magallanes
-
6. Version control
- 6.1 Git-flow
- 6.2 Main branches
- 6.3 Feature branches
- 6.4 Release branches
- 6.5 Hotfix branches
- 6.6 Labs branches
-
7. Dependencies
- 7.1 Semantic Versioning
- 7.2 Version control
- 7.3 Development dependencies
- 7.4 The composer.lock file
- 7.5 Composer and github rate limit
-
8. Database migrations
- 8.1 Installation & configuration
- 8.2 Migration files
- 8.3 Possible data loss on rollbacks
- 8.4 Batches
-
9. Running tests
- 9.1 Unit testing
- 9.2 Acceptance testing
- 9.3 End-to-end testing
- 9.4 Manual testing
- 9.5 What, where and when
- 9.6 Failing tests
-
10. Logs and notifications
- 10.1 Saving logs
- 10.2 Types of notification
- 10.3 Useful git commands
- Conclusion
- Notes
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $13 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
