Heroku Cookbook

Heroku Cookbook

By : Mike Coutermarsh

Buy this Book

Heroku Cookbook

By: Mike Coutermarsh

Buy this Book

Overview of this book

Heroku is a Platform as a Service that enables developers to rapidly deploy and scale their web applications. Heroku is designed for developer happiness, freeing developers from doing system administrative tasks such as configuring servers and setting up load balancers. Developers are able to focus on what they do best, building web applications, while leaving the details of deployment and scaling to the experts at Heroku. This practical guide is packed with step-by-step solutions to problems faced by every production-level web application hosted on Heroku. You'll quickly get comfortable with managing your Heroku applications from the command line and then learn everything you need to know to deploy and administer production-level web applications.

Heroku Cookbook

Credits

About the Author

About the Reviewers

www.PacktPub.com

Preface

Free Chapter

Getting Started with Heroku

Introduction

Installing the Heroku Toolbelt

Introducing version control with Git

Deploying a Rails application to Heroku

Deploying a Node.js application to Heroku

Introducing dynos, workers, and scaling

Managing Heroku from the Command Line

Introduction

Viewing application logs

Searching logs

Installing add-ons

Managing environment variables

Enabling the maintenance page

Managing releases and rolling back

Running one-off tasks and dynos

Managing SSH keys

Sharing and collaboration

Monitoring load average and memory usage

Setting Up a Staging Environment

Introduction

Duplicating an existing application

Managing git remotes

Password protection for a Rails app

Deploying with Heroku labs – Pipeline

Deploying from tags

Continuous integration and deployment with Travis CI

Production-ready with Heroku

Introduction

Managing domains from the command line

Configuring DNS with CloudFlare

Setting up SSL with CloudFlare

Enabling preboot for seamless deploys

Enabling custom maintenance and error pages

Setting up a status page

Setting up log draining with LogEntries

Error Monitoring and Logging Tools

Introduction

Checking Heroku's status

Adjusting Rails's logging level

Storing historical logs with PaperTrail

Monitoring for 404 and 500 errors with PaperTrail

Logging slow queries with PaperTrail

Monitoring uptime with Pingdom

Logging errors with Rollbar

Load Testing a Heroku Application

Introduction

Monitoring dyno performance with Librato

Monitoring application performance with New Relic

Learning to load test with Siege

Configuring complex load tests with Siege

Load testing from the cloud with Blitz.io

Testing real-user scenarios with Load Impact

Optimizing Ruby Server Performance on Heroku

Introduction

Setting up and running Unicorn on Heroku

Monitoring and tuning Unicorn's memory usage

Tuning Unicorn's backlog for Heroku

Timing out long requests with Unicorn

Setting up and running Puma on Heroku

Running Puma with Rubinius for parallelism

Optimizing a Rails Application on Heroku

Introduction

Setting up a sample blogging app

Using Heroku Deflater to gzip assets

Serving assets from Amazon Web Services (AWS) Cloudfront

Adding memcached to a Rails application

Adding Redis to a Rails application

Implementing low-level caching in Rails

Caching rendered views

Aborting long requests with Rack::Timeout

Using a follower for read-only DB queries

Using and Administrating Heroku Postgres

Introduction

Creating and sizing a new database

Promoting a Heroku database

Connecting to Heroku Postgres from Navicat

Connecting to Heroku Postgres from psql

Creating a database backup

Restoring from a backup

Creating a read-only follower

Viewing and stopping database processes

Analyzing Heroku Postgres's performance

The Heroku Platform API

Introduction

Making our first API request with HTTPie

Getting started with the Platform API gem

Scaling dynos and workers

Managing configuration variables

Adding and removing collaborators

Creating new Heroku applications

Index

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Monitoring for 404 and 500 errors with PaperTrail

We can set up various searches in PaperTrail and have it automatically e-mail a summary of all the events that match our search for the day. In this recipe, we will learn how to set up a search for specific HTTP status codes and have PaperTrail e-mail us when they are set up.

Note

We'll need PaperTrail set up for this recipe; refer to the previous recipe if you do not have it set up yet.

How to do it…

To start, we'll need to open up a terminal and navigate to our Heroku project with PaperTrail installed. Then, we can perform the following steps:

First, let's open up the PaperTrail dashboard. We can quickly do this from the command line:
```
$ heroku addons:open papertrail
```
Now, we want to create a search for all the events that resulted in a 404 (Not Found) or 500 (Internal Server Error) HTTP response code. We can do this by typing status=404 OR status=500 into the search box at the bottom of the page.
Next, let's click on Search, and we'll see the...

Heroku Cookbook

By : Mike Coutermarsh

Heroku Cookbook

By: Mike Coutermarsh

Overview of this book

Related Content you might be interested in

Current Title:

Heroku Cookbook

Monitoring for 404 and 500 errors with PaperTrail

Note

How to do it…