| #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] |
| #require 'rubygems' | |
| require 'pp' | |
| #require 'ap' # Awesome Print | |
| class Object | |
| # expects [ [ symbol, *args ], ... ] | |
| def recursive_send(*args) | |
| args.inject(self) { |obj, m| obj.send(m.shift, *m) } | |
| end | |
| end |
| def parse_data | |
| # This is a typical set of parameters passed by Facebook | |
| # Parameters: {"signed_request"=>"vsSe9NNeyqom0hAtGyb2L9scc3-aNbY5Xb25EW55LpE.eyJhbGdvcml0aG0iOiJITUFDLVNIQTI1NiIsImV4cGlyZXMiOjEzMDA3NzAwMDAsImlzc3VlZF9hdCI6MTMwMDc2NDg2Niwib2F1dGhfdG9rZW4iOiIxNzE2MDQwOTI4NjgwNTd8Mi4xQnBWNm5mU2VXRm5RT0lOdzltNWFRX18uMzYwMC4xMzAwNzcwMDAwLTE1MjAwMzkxfEFpNXctc2t4WlJyVUd1ZzZvOU95aDZBQmdSZyIsInVzZXIiOnsiY291bnRyeSI6InVzIiwibG9jYWxlIjoiZW5fVVMiLCJhZ2UiOnsibWluIjoyMX19LCJ1c2VyX2lkIjoiMTUyMDAzOTEifQ"} | |
| # If we have the signed_request parameters, stash them away | |
| session[:signed_request] = params[:signed_request] if params[:signed_request] | |
| encoded_user_data = session[:signed_request] | |
| return if encoded_user_data.blank? | |
By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:
/people/6
But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.
| require File.join(File.dirname(__FILE__), 'deploy/nginx') | |
| require File.join(File.dirname(__FILE__), 'deploy/log') | |
| default_run_options[:pty] = true | |
| set :ssh_options, { :forward_agent => true } | |
| set :application, "appname" | |
| set :repository, "git@giturl" | |
| set :scm, :git |
| # See rails source: | |
| # https://github.com/rails/rails/blob/master/actionpack/lib/action_controller/caching/pages.rb | |
| # | |
| # Turn on caching in development, by changing this line to true in config/environments/development.rb: | |
| # | |
| # config.action_controller.perform_caching = true | |
| # | |
| # Then run: | |
| # | |
| # bundle exec rake pages:cache |
| # USAGE: Hash.from_xml:(YOUR_XML_STRING) | |
| # | |
| # - fixes handling of <text> elements | |
| # - prepends namespaces on keys where used including both elements & attributes | |
| # - uses strings instead of symbols to prevent consumption of the symbol table | |
| require 'nokogiri' | |
| # modified from http://stackoverflow.com/questions/1230741/convert-a-nokogiri-document-to-a-ruby-hash/1231297#1231297 | |
| class Nokogiri::XML::Node | |
| def namespaced_name |
| require 'socket' # Sockets are in standard library | |
| server = TCPServer.new(1234) | |
| begin | |
| while connection = server.accept | |
| while line = connection.gets | |
| break if line =~ /quit/ | |
| puts line | |
| connection.puts "Received!\n" | |
| end |
| <?xml version="1.0" encoding="UTF-8"?> | |
| <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> | |
| <modelVersion>4.0.0</modelVersion> | |
| <groupId>com.example</groupId> | |
| <artifactId>my-project</artifactId> | |
| <version>0.0.1-SNAPSHOT</version> | |
| <dependencies> | |
| <!-- none yet --> |
I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.
If you want to roll up all of these into a single jQuery plugin check out Sharrre
Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.
