swaroopch

#!/bin/bash

function flask-boilerplate-tmux
{
    # https://github.com/swaroopch/flask-boilerplate
    BASE="$HOME/code/flask-boilerplate"
    cd $BASE

    tmux start-server
    tmux new-session -d -s flaskboilerplate -n model

unnitallman

require 'active_record'

ActiveRecord::Base.logger = Logger.new(STDERR)
ActiveRecord::Base.colorize_logging = false

ActiveRecord::Base.establish_connection(
    :adapter => "sqlite3",
    :dbfile  => ":memory:"
)

ramontayag

class MenuEditor::Page::FormWidget < Apotomo::Widget
  # Step 1: make sure the current_user variable (or something like it) is available for use
  include Devise::Controllers::Helpers
  helper_method :current_user
  responds_to_event :submit

  def display
    ...
  end

stream7

 literally always have to look up the meaning of :limit in migrations when it comes to integer values. Here's an overview. Now let's memorise it (oh, this works for MySQL, other databases may work differently):

:limit	    Numeric Type	Column Size	Max value
1	     tinyint	         1 byte	          127
2	     smallint	         2 bytes	32767
3	     mediumint	         3 byte	        8388607
nil, 4, 11    int(11)	         4 byte	       2147483647
5..8	      bigint	         8 byte	     9223372036854775807

Note: by default MySQL uses signed integers and Rails has no way (that I know of) to change this behaviour. Subsequently, the max. values noted are for signed integers.

elight

#!/usr/bin/env ruby

CHARACTERS = (('A'..'Z').to_a + ('a'..'z').to_a + (0..9).to_a)
GROUP = 53
MY_MACHINE_DYNDNS_ADDRESS = "Put your DynDns DNS name here"
MY_SSH_PORT = "Your router's external port that will forward to SSH" # as a Fixnum


def ridiculous_password
  (1..20).map do

tjh

#!/usr/bin/env ruby

# Put this file in the root of your Rails project,
# then run it to output the SQL needed to change all
# your tables and columns to the same character set 
# and collation.
#
# > ruby character_set_and_collation.rb

DATABASE      = ''

coreyhaines

--colour
-I app

isc

Twitter Bootstrap Components Helper

Provides an accordion helper and a tabs helper

In your Gemfile:

gem 'bootstrap-components-helpers', :git => 'git://gist.github.com/2117187.git'

Accordion helper:

tansengming

# How Clearance / Hoptoad does it
module Clearance
  class << self
    attr_accessor :configuration
  end

  def self.configure
    self.configuration ||= Configuration.new
    yield(configuration)
  end

cpjolicoeur

I'm hunting for the best solution on how to handle keeping large sets of DB records "sorted" in a performant manner.

Problem Description

Most of us have work on projects at some point where we have needed to have ordered lists of objects. Whether it be a to-do list sorted by priority, or a list of documents that a user can sort in whatever order they want.

A traditional approach for this on a Rails project is to use something like the acts_as_list gem, or something similar. These systems typically add some sort of "postion" or "sort order" column to each record, which is then used when querying out the records in a traditional order by position SQL query.

This approach seems to work fine for smaller datasets, but can be hard to manage on large data sets with hundreds (or thousands) of records needing to be sorted. Changing the sort position of even a single object will require updating every single record in the database that is in the same sort group. This requires potentially thousands of wri