laserlemon

# Activate the gem you are reporting the issue against.
gem 'rails', '4.0.3'

require 'rails'
require 'action_controller/railtie'

class TestApp < Rails::Application
  config.root = File.dirname(__FILE__)
  config.session_store :cookie_store, key: 'cookie_store_key'
  config.secret_token    = 'secret_token'

laserlemon

#include <math.h>
#define PI 3.1415926535897932384626433832795
 
/****************************************
Example Sound Level Sketch for the 
Adafruit Microphone Amplifier
****************************************/
 
const int sampleWindow = 50; // Sample window width in mS (50 mS = 20Hz)
const int led1 = 9;          // the pin that the LED is attached to

laserlemon

Keybase proof

I hereby claim:

• I am laserlemon on github.
• I am laserlemon (https://keybase.io/laserlemon) on keybase.
• I have a public key whose fingerprint is 98E1 8104 6431 0662 6353 2005 0B2D B485 5693 2D75

To claim this, I am signing this object:

laserlemon

[12:06pm] laserlemon: hello!
[12:06pm] svninfo: laserlemon: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.
[12:09pm] laserlemon: i have a question about git hooks. anybody up for it?
[12:09pm] laserlemon: i’m wondering if server-side clone hooks are anywhere on the roadmap
[12:10pm] ojacobson: laserlemon: what would the semantics be?
[12:10pm] ojacobson: (keep in mind that, from git's point of view, clone, fetch, and ls-remote are indistinguishable)
[12:10pm] laserlemon: i actually don’t know a lot about git hooks as it is, so i’m not sure
[12:11pm] Eugene: No, they are not.
[12:11pm] laserlemon: maybe it’d be useful to hear my use case
[12:12pm] Eugene: You 

laserlemon


Simple, Heroku-friendly Rails app configuration using ENV and a single YAML file

laserlemon

What is an Interactor?

An interactor is a simple, single-purpose object.

Interactors are used to encapsulate your application's business logic. Each interactor represents one thing that your application does.

Context

An interactor is given a context. The context contains everything the interactor needs to do its work.

laserlemon

# my_gem/cli.rb

require "thor"

require "my_gem/cli/foo_bar"
require "my_gem/cli/foo_baz"
require "my_gem/cli/install"

module MyGem
  class CLI < Thor

laserlemon

Keybase proof

I hereby claim:

• I am laserlemon on github.
• I am laserlemon (https://keybase.io/laserlemon) on keybase.
• I have a public key whose fingerprint is CDB6 894C 1DA5 35AB 8425 DD90 C650 CD1B 7189 C7DF

To claim this, I am signing this object:

laserlemon

class FinishOptimization
  include Interactor::Organizer
  
  organize CommitImages
  organize PushImages,
           CreateOrUpdatePullRequest,
           MarkAsFinished, if: -> { context.optimized_commit_sha }
end

laserlemon

class PlaceOrder
  include Interactor
  
  # What goes here?
  
  before do
    context.user ||= User.find(context.user_id)
  end
  
  def call