wookiehangover

Geeks Who Drink: Motherbrain Rounds and Questions Schema

Currently there are several changes to Motherbrain needed to accomodate the mobile and Quizmaster applications.

Round Types

During the course of a quiz, it's necessary for the mobile app and Quizmaster dashboard to be able to determine the type of Round being played.

These are the following round types:

Akkuma

passport = require 'passport'
googOID  = require('passport-google').Strategy
steamOID = require('passport-steam').Strategy

passport.use new steamOID 
		returnURL: 'http://localhost:3000/auth/steam/return'
		, realm: 'http://localhost:3000'
		, () -> console.log arguments

passport.use new googOID 

acao

var bcrypt = require('bcrypt');

load('application');

before(loadUser, {only: ['show', 'edit', 'update', 'destroy']});
before(loadGroups, {only: ['new', 'edit']});

action('new', function () {
    this.title = 'New user';
    this.user = new User;

KevinTriplett

# add this file capybara_wait_until.rb to your /test directory

module Capybara
  class Session
    ##
    #
    # Retry executing the block until a truthy result is returned or the timeout time is exceeded
    #
    # @param [Integer] timeout   The amount of seconds to retry executing the given block
    #

mhuggins

source 'https://rubygems.org'

gem 'prawn'
gem 'gruff'

brandonc

module BatchJobStateful
  extend ActiveSupport::Concern

  included do
    field :current_batch_id, type: String
    field :last_batch_total, type: Integer
    field :last_batch_failures, type: Integer
    field :last_batch_created_at, type: Time
    field :last_batch_completed_at, type: Time
  end

sebmarkbage

You're probably getting this warning because you're accessing methods on a component before it gets mounted. This will be soon be an unsupported use case.

The component that gets created by invoking the convenience constructor MyComponent(props, children) or using the JSX syntax <MyComponent /> is not guaranteed to be the instance that actually gets mounted. It's a description of what the actual mounted instance should look like.

Anti-pattern:

The component also doesn't have access to state or other important information such as the final props. As a consequence you shouldn't be calling custom methods on this object.

var MyComponent = React.createClass({

mndoci

# via http://blog.zerosum.org/2011/03/02/better-aws-access-control-with-iam-and-fog.html

require 'fog'

username = 'testuser'
bucket = 'uniquebucketname1234'

aws_credentials = { 
  :aws_access_key_id => 'YOUR-ACCESS-KEY-ID',   
  :aws_secret_access_key => 'YOUR-SECRET-ACCESS-KEY'

kagemusha

Tested on: Rails 3.1, Mongoid 2.0.1, pg 0.12.0 gem

Migrate from Mongo to PG
1. remove mongoid gem
2. add pg gem
3. in application.rb re-add ActiveRecord
4. for all models
- inherit from ActiveRecord::Base
- get rid of Mongoid:Document line
- make migrations and put fields there

killercup

# # Frontend Build Process

path = require('path')
gulp = require('gulp')
gutil = require('gulp-util')
plumber = require('gulp-plumber')

webpack = require("webpack")

# ## CONSTS