Forked from https://gist.github.com/eric1234/5628416
Adjustments:
- No environment based .env filenames
- No need for APP_ENV
Forked from https://gist.github.com/eric1234/5628416
Adjustments:
site :opscode | |
cookbook 'apt' | |
cookbook 'statsd', git: 'https://github.com/librato/statsd-cookbook.git' | |
cookbook 'graphite', git: 'https://github.com/hw-cookbooks/graphite.git' |
# | |
# Assumes an independent box (we'll call this one "graphite") | |
# | |
# Stay up to date | |
sudo apt-get update | |
sudo apt-get upgrade | |
# Install git | |
sudo apt-get install g++ curl libssl-dev -y |
*node_modules/ | |
.DS_Store |
Some json configurations will emit a single root node named after the object's type or an abstractable name for the object depending on context. This document outlines the differences and examples of both included and discluded root nodes in JSON responses.
Nodes of this type, for request GET foos
will respond with this body:
{
"foo": {
"bar": "baz"
}
# etc ... | |
group :development do | |
# etc ... | |
# Sprites: | |
gem 'sprite-factory' | |
gem 'rmagick' | |
gem 'piet' # image optimization | |
end |
// DEBUG Styles: | |
#time_of_day_debug { | |
position: fixed; | |
padding: .25em; | |
bottom: 0; | |
right: 0; | |
font-size: 10px; | |
> a { | |
display:block; | |
margin: .5em .5em .5em 1.1em; |
# If sent as normal errors: | |
# Response: {"errors": { "email": ["Email address is invalid","Email address can't be blank"]} } | |
>> NewsletterSubscriber.new(:email_address => "").save | |
ArgumentError: wrong number of arguments(2 for 1) | |
from /Users/amoslanka/.rvm/gems/ruby-1.9.3-p194/gems/activeresource-3.2.8/lib/active_resource/validations.rb:19:in `[]' | |
from /Users/amoslanka/.rvm/gems/ruby-1.9.3-p194/gems/activeresource-3.2.8/lib/active_resource/validations.rb:19:in `block (2 levels) in from_array' | |
from /Users/amoslanka/.rvm/gems/ruby-1.9.3-p194/gems/activeresource-3.2.8/lib/active_resource/validations.rb:18:in `each' | |
from /Users/amoslanka/.rvm/gems/ruby-1.9.3-p194/gems/activeresource-3.2.8/lib/active_resource/validations.rb:18:in `detect' | |
from /Users/amoslanka/.rvm/gems/ruby-1.9.3-p194/gems/activeresource-3.2.8/lib/active_resource/validations.rb:18:in `block in from_array' |
PG::Error: ERROR: relation "chores" does not exist | |
LINE 4: WHERE a.attrelid = '"chores"'::regclass | |
^ | |
: SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull | |
FROM pg_attribute a LEFT JOIN pg_attrdef d | |
ON a.attrelid = d.adrelid AND a.attnum = d.adnum | |
WHERE a.attrelid = '"chores"'::regclass | |
AND a.attnum > 0 AND NOT a.attisdropped | |
ORDER BY a.attnum | |
/Users/amoslanka/.rvm/gems/ruby-1.9.3-p194@jitb_cms/gems/activerecord-3.2.7/lib/active_record/connection_adapters/postgresql_adapter.rb:1158:in `async_exec' |