/ on Instagram http://instagr.am/p/RDXc2ELahQ/
Ruby on Rails Developer
/ on Instagram http://instagr.am/p/RDXc2ELahQ/
Sounds disappointed.
ToS;DR aims at creating a transparent and peer-reviewed process to rate and analyse Terms of Service and Privacy Policies in order to create a rating from Class A to Class E.
Its really surprising how many terms of service agreements give you “no right to leave the service”.
That about sums up the 2012 Red Sox.
We’ve been working with Twitter over the last few days to try to work around this limit for the duration of the beta but have been unable to come up with solution that was acceptable to them.
I’m guessing that was a short mostly one-sided conversation.
quiet assets is a gem that cuts down on asset pipeline log spam. I used to do this with an initializer but this is much easier.
With quiet assets:
gem 'quiet_assets', :group => :development
Then:
bundle
Quiet assets also lets you turn asset pipeline log suppression off with config.quiet_assets
if Rails.env.development?
Rails.application.assets.logger = Logger.new('/dev/null')
Rails::Rack::Logger.class_eval do
def call_with_quiet_assets(env)
previous_level = Rails.logger.level
Rails.logger.level = Logger::ERROR if env['PATH_INFO'] =~ %r{^/assets/}
call_without_quiet_assets(env)
ensure
Rails.logger.level = previous_level
end
alias_method_chain :call, :quiet_assets
end
end
Using yaml file to store information such as S3 keys, and email passwords and then adding it to your .gitignore is a great way to keep sensitive information out of a git repository.
There’s a gotcha though: If you load it as a constant from an initializer then use that constant in another initializer and that initializer is loaded before the config, the constant is not going to exist and your app is going to crash. The Ruby on Rails Configuration Guide recommends prefixing the initializer filename with a number to control the load order of critical files. e.g. 01_important.rb
Another way to do this is to simply require the config in any initializer that uses the constant like so:
require "#{Rails.root}/config/initializers/load_config.rb" unless defined?(APP_CONFIG)
Normalize.css is a customisable [sic] CSS file that makes browsers render all elements more consistently and in line with modern standards. We researched the differences between default browser styles in order to precisely target only the styles that need normalizing.
Since it is used in Twitter Bootstrap, I’ve been using normalize inadvertently for months. But recently, I have started to use normalize in projects where I’m not using Bootstrap instead of a plain old CSS reset. I think it saves time and lets you take advantage of some useful defaults. You can check out the code on github or look at the demo.
Compare it to a typical CSS reset and its clear how much easier it could be to start with normalize.
Mike Ehrmantraut
Weapons of choice:
* Guns, fists
* Droopy murder eyes
A guide to understanding Version 1.1 of the Twitter API