Laravel 5.1 Beauty - Introduction

A brief introduction on my new book about Laravel 5.1

Posted on February 21, 2015 in L5 Beauty

Chapter Contents

Long Term Support

Laravel version 5.1 is the first LTS (long term support) Laravel release. This means bug fixes are provided for 2 years and security fixes are provided for 3 years.

This is important because the applications you build today will still be supported by the framework tomorrow.

Why This Book

My previous book on Laravel, Getting Stuff Done with Laravel 4 was well received. Now that Laravel 5.1 is available, I briefly thought of updating the book to work with Laravel 5.1. The new version of Laravel implements big changes from Laravel 4, but Laravel 5.1 is mostly backwards compatible.

But the Getting Stuff Done with Laravel 4 book isn’t really a manual covering every aspect of Laravel 4. It’s a process and design book. The principles discussed within that book still are valid in Laravel 5.1, even if the implementation may vary slightly.

Instead of updating my previous book, I’m creating a new book, Laravel 5.1 Beauty, to highlight some of the new features. This book is bigger and better than my previous book.

GitHub and the Blog

I’m publishing Laravel 5.1 Beauty simultaneously, as it is being built, on my web site and on Leanpub.

The Source Code is on GitHub

The source code for the application built in this book is available on GitHub at ChuckHeintzelman/l5beauty. Just switch the branch at github to the chapter you’re working on.

This book has a different tone than my previous book. No lame attempts to be funny. (I guess we all can’t be Dayle Rees.)

Laravel 5.1 Beauty goes through the process of creating, designing and coding a real-world application while focusing on the the architecture that makes Laravel the number one PHP framework available today.

What is the Application?

Throughout this book we’ll build a simple, clean and beautiful blogging application and the administration required to maintain the blog.

My own Laravel blog,, uses the same blogging application developed here.

Conventions Used This Book

There are a few conventions used throughout this book.

Code is indented two spaces

The standard indentation for PHP code is 4 spaces. Since this book is available in a variety of ebook formats and some devices with small screens don’t have much horizontal space, code is indented 2 spaces instead of 4 in this book to save space.

for ($i = 1; $i <= 10; $i++) {
  echo "I can count to $i\n";

Lines that end with backslash(\) should be continued

If you see any line ending with a backslash, that means the code should continue uninterrupted with text from the next line.

$ here_is_a_really_really_long_command that_has_a_long list of_arguments\
which should continue

In the above line, even though two lines are shown you should type in everything, excluding the backlash into one line.

Be Careful of This One

When you’re typing code and miss this it can cause an issue. When in doubt check the GitHub Repository switching branches to the Chapter you’re currently working on.

Different prompts between Windows, OS X (or Linux), and Homestead

Whenever a Windows command prompt is used, the prompt always begins with C: and ends with the > symbol.


Whenever the OS X Console or Linux console is used, the prompt also ends with the > symbol, but slashes are used instead of backslashes and often there’s a tilde ~ in the path.


Whenever the console is generic (meaning it could be Windows, OS X, or Linux console depending on your host operating system) a prompt ending with a percent sign % is used.


Finally, whenever the console for the Homestead Virtual Machine is used, the standard dollar sign $ prompt is used. (The majority of the book uses the Homestead Virtual Machine.)


With the Homestead Virtual Machine, your prompt actually shows the username and hostname before the path. For example: vagrant@homestead:~$, but the username and hostname are only occasionally illustrated.

Sometimes the path is missing

Whenever the path is omitted from the prompt in one of the versions of the console windows, it is assumed you are in the current project directory.

Have Fun

I hope you enjoy this book and learn some of the highlights with Laravel 5.1 through it. Be sure and follow along, set up your development machine, and create the application step-by-step, chapter-by-chapter.

Above all. Have fun. Coding in Laravel 5.1 is great fun.

comments powered by Disqus