With RVM installed, I like to maintain a gemset called new_projects. This has whatever rails version I want to be creating new projects with.
$ rvm 1.9.3@new_projects --verbose --create
$ gem install rails
#Deploy and rollback on Heroku in staging and production | |
task :deploy_staging => ['deploy:set_staging_app', 'deploy:push', 'deploy:restart', 'deploy:tag'] | |
task :deploy_production => ['deploy:set_production_app', 'deploy:push', 'deploy:restart', 'deploy:tag'] | |
namespace :deploy do | |
PRODUCTION_APP = 'YOUR_PRODUCTION_APP_NAME_ON_HEROKU' | |
STAGING_APP = 'YOUR_STAGING_APP_NAME_ON_HEROKU' | |
task :staging_migrations => [:set_staging_app, :push, :off, :migrate, :restart, :on, :tag] | |
task :staging_rollback => [:set_staging_app, :off, :push_previous, :restart, :on] |
These are the metrics that would be used by the engineering team to evaluate effectiveness of front-end optimizations, and shouldn’t be communicated to stakeholders. Emily’s 90% page loaded metric is a way better model for measurable progress of “page load time”.
The purpose of this document is to outline the main metrics we use when discussing various end-user performance measurements such as "page speed".
Fig 1) A diagram we have been using in conversations to help illustrate the various events
and how they inter-relate.
require 'myclass' | |
traceable = MyClass.CreateTraceableObject() |