kany

# see http://stackoverflow.com/questions/5880962/how-to-destroy-jobs-enqueued-by-resque-workers - old version
# see https://github.com/defunkt/resque/issues/49
# see http://redis.io/commands - new commands

namespace :resque do
  desc "Clear pending tasks"
  task :clear => :environment do
    queues = Resque.queues
    queues.each do |queue_name|
      puts "Clearing #{queue_name}..."

kany

mkdir -p ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/CoffeeScript
cd ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/CoffeeScript
curl -O https://raw.github.com/jashkenas/coffee-script-tmbundle/master/Syntaxes/CoffeeScript.tmLanguage
curl -O https://raw.github.com/jashkenas/coffee-script-tmbundle/master/Preferences/CoffeeScript.tmPreferences

kany

select 
    concat(table_name, '.', column_name) as 'foreign key',  
    concat(referenced_table_name, '.', referenced_column_name) as 'references'
from
    information_schema.key_column_usage
where
    referenced_table_name is not null AND
    referenced_table_name = 'org_units';

kany

Change to root directory
1) cd /

See size of each file/folder in directory with sorting
2) sudo du -sh * | sort -gr

If /SomeFolder is over 1gb
3) cd SomeFolder && sudo du -sh *

kany

This method only works if currently logged in as root.  Sometimes when working with older ruby 'mysql' gems, after the 'mysql' gem is installed, the previous password doesn't work.

1) Already logged into Mysql
2) gem jacked up your mysql password
3) mysql > use mysql;
4) mysql > UPDATE user SET Password=PASSWORD('') WHERE User='root'; FLUSH PRIVILEGES;

kany

Search git logs for tickets = 5803,5804,or5805 using regex.

http://gitready.com/advanced/2009/01/20/bend-logs-to-your-will.html

git log --grep=580[345] --stat -p --author=frank

kany

Taming GIT

Using Git - and Git Flow
First up: Git for Agile Teams (pdf) should be considered required reading :)

Second, keep this diagram in mind while reading the following text (image source)


Git Flow
There is nothing special about Git Flow - everything is still commits, branches and tags, but the toolset does add some convenient shortcuts for common operations. Examples include making a hotfix for the current production version, and keeping track of multiple features under concurrent development. Git Flow does nothing special to commits, nor are the branches any different from branches you create by other means. A strict naming standard does make things easier to follow, though.

kany

# Add 'config.development_environments = []' to config/initializers/airbrake.rb
Airbrake.configure do |config|
  config.api_key          = "1234"
  config.environment_name = AppConfig.environment if AppConfig.environment
  config.secure           = true
  config.development_environments = []
end

# Test it out in the console
1) rails console

kany

1) rails c
2) YAML::ENGINE.yamler = 'syck'
3) y @user.participant

--- !ruby/object:Participant 
attributes: 
  id: 9
  employee_hashed_ssn: "hashed ssn: 00001"
  ch_member_id: 100
  first_name: Test Employee 00001

kany

http://www.wyliethomas.com/blog/2011/08/24/rvm-rake-and-cron-on-ubuntu/

RVM, Rake and Cron on Ubuntu
by admin on August 24th, 2011
Tennnngh! I read countless blog posts, tried numerous approaches that I found and rebuilt the server more than a couple times. And finally I found what the missing piece was for getting a rake command to run in cron with rvm.

Most of the results I found (on stackoverflow) flagged the solution as adding the path to your rvm in your line item in crontab. Something like /home/username/.rvm/gems/rake my_awesome_task… etc. I tried every variation of that I could think of and got the same results.

I dont use cron every day so this was a revelation to me. I found out that you can set variables, environment variables in your crontab file.