jhjguxin jhjguxin

Rails cache (dalli) snippet

base on guanxi.me
author: Francis Jiang

usual case

def smart_fetch(name, options, &blk)
  options = HashWithIndifferentAccess.new(options)

Prevent unlimited increse of space used by mongo logdb

through Repeated use collection name

6.months.ago.to_date.upto(Date.today)

def generate_syslog_collection_name(date = nil, mod_size = 60)
  date = date.try(:to_date)
  if date.is_a?(Date)
    mod_num = Date.new(2000).upto(date).count % mod_size

How auth2 test with faraday

resources

the problems

byobu-tmux

sudo apt-get install screen byobu

Byobu包装过的Tmux将其配置文件放在了「~/.byoburc.tmux」下面，因此编辑这个文件，写如以下内容：

set-window-option -g mode-keys vi bind C-h select-pane -L

Config Rails 3 with dalli(memcahed)

To install dalli in your Rails 3 app, simply add the following to your Gemfile and run bundle install.

# Gemfile
gem "dalli", "~> 2.6.4",   :platforms => :ruby

To setup Rails to use the Dalli client for production, add the following to config/environments/production.rb:

Implement Routing for Subdomains

Rails 3.0 introduced support for routing constrained by subdomains.

A subdomain can be specified explicitly, like this:

match '/' => 'home#index', :constraints => { :subdomain => 'www' }

ghost with heroku

install heroku

wget -qO- https://toolbelt.heroku.com/install-ubuntu.sh | sh

heroku login

get ghost

http://guides.rubyonrails.org/generators.html#creating-generators-with-generators

rails generate generator --help
rails generate generator setup_config

First, notice that we are inheriting from Rails::Generators::NamedBase instead of Rails::Generators::Base. This means that our generator expects at least one argument, which will be the name of the initializer, and will be available in our code in the variable name.

MySQL Engines - MyISAM vs Innodb

When MyISAM tables are seen to be mostly useful?

There can be several other reasons that fit your requirement for choosing the MyISAM engine. For example reads can be faster on MyISAM vs Innodb despite what the general claims on the above two links when MyISAM table has fixed (not dynamic) row size i.e. when it uses more CHARs for example versus VARCHARs. Still there could be other reasons besides this why you choose or have chosen MyISAM over Innodb. Another reason why you may have chosen MyISAM over Innodb is perhaps due to the fact that Innodb must perform additional checks owing to its ACID compliant nature - so for example a FK check needs to be checked which could potentially cause an operational overhead. Unless you ha

	require 'my-sinatra-app'
	require 'sinatra/activerecord/rake'

	desc "run irb console"
	task :console, :environment do \|t, args\|
	ENV['RACK_ENV'] = args[:environment] \|\| 'development'

	exec "irb -r irb/completion -r my-sinatra-app"
	end