Book Image

Heroku Cookbook

By : Mike Coutermarsh
Book Image

Heroku Cookbook

By: Mike Coutermarsh

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.

Related Content you might be interested in

Current Title:

Small book image
Heroku Cookbook
Mike Coutermarsh
Nov, 2014 | 232 pages
No titles found
Table of Contents (17 chapters)
Heroku Cookbook
Heroku Cookbook
Credits
Credits
About the Author
About the Author
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Getting Started with Heroku
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
2
Managing Heroku from the Command Line
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
3
Setting Up a Staging Environment
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
4
Production-ready with Heroku
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
5
Error Monitoring and Logging Tools
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
6
Load Testing a Heroku Application
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
7
Optimizing Ruby Server Performance on Heroku
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
8
Optimizing a Rails Application on Heroku
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
9
Using and Administrating Heroku Postgres
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
10
The Heroku Platform API
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
Index

Caching rendered views

Rendering a page in Rails isn't a simple process. It usually consists of several database queries that render various partials and convert HAML to HTML. Repeating this entire process for each page load is wasteful. In this recipe, you will learn how to cache your views so that you only have to render them once. You'll also learn how to use key-based cache expiration to ensure that you're always serving the latest content.

How to do it…

In this recipe, we'll use the Blogger application as an example to implement view caching. This time, we will optimize posts#show using caching to make viewing a post as fast as possible.

Note

Make sure that caching is enabled in config/environments/development.rb and config.action_controller.perform_caching is set to true.

  1. Currently, if we try to view a post, our application does the following to render the page:

    Started GET "/posts/2" for 127.0.0.1 at 2014-08-09 14:29:06 -0400
Processing by PostsController#show as HTML
  Parameters: {"id...
Previous Section
End of Section 9
Next Section