Book Image

Mastering Yii

By : Charles R. Portwood ll
Book Image

Mastering Yii

By: Charles R. Portwood ll

Overview of this book

The successor of Yii Framework 1.1, Yii 2 is a complete rewrite of Yii Framework, one of the most popular PHP 5 frameworks around for making modern web applications. The update embraces the best practices and protocols established with newer versions of PHP, while still maintaining the simple, fast, and extendable behavior found in its predecessor. This book has been written to enhance your skills and knowledge with Yii Framework 2. Starting with configuration and how to initialize new projects, you’ll learn how to configure, manage, and use every aspect of Yii2 from Gii, DAO, Query Builder, Active Record, and migrations, to asset manager. You'll also discover how to automatically test your code using codeception. With this book by your side, you’ll have all the skills you need to quickly create rich modern web and console applications with Yii 2.
Table of Contents (20 chapters)
Mastering Yii
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
5
Modules, Widgets, and Helpers
13
Debugging and Deploying
Index

Deploying


The final step in working with any Yii2 application is to move it to production and create a deployment strategy. There are many different tools that we can use to deploy our code, ranging from Bamboo, TravisCI, Jenkins, Capistrano, and even manual SSH deployments—just to name a few.

In general, however, there are several key concepts we should keep in mind when deploying our code:

  • Deployments should be automated and hands off. In order to be consistent, your deployments should be run by a tool or service that can run the same tasks every time. This eliminates any human error during the deployment and ensures consistency.

  • Deployments should be fast, providing you with the ability to quickly push out new features and bug fixes.

  • The actual building of your application (such as combined and compressed JavaScript, CSS, and other configurations) should occur on a build server and then be pushed to your production server in a pre-build manner. This ensures that your production servers don...