| namespace :db do | |
| desc 'Seed database from db/seed.sql file instead of the traditional db/seed.rb' | |
| namespace :seed do | |
| config = Rails::Configuration.new.database_configuration[RAILS_ENV] | |
| seed_sql = File.expand_path(File.dirname(__FILE__) + '/../../db/seed.sql') | |
| if !File.exists?(seed_sql) | |
| puts "Missing RAILS_ROOT/db/seed.sql" |
| # when I write new blog posts I usually have a temporary folder called new_post on my desktop | |
| # that I place images I want to upload to amazon s3 (which is distributed as CF) and then | |
| # get the appropriate URLs to put the images in my blog post | |
| # I usually save files as some_slug.png and some_slug_1200.png | |
| # with the latter being a larger version (1200px wide) of the first. | |
| # a typical upload will include 20 files. 2 versions of some (sm and lg), and some orphans | |
| # so this compares filenames and if it detects a larger version of a file, | |
| # it links the the smaller image to the larger image (i use fancyzoom on my site) | |
| # if not, it just links to the image |
| RED="\[\033[01;31m\]" | |
| GREEN="\[\033[01;32m\]" | |
| COLOR_NONE="\[\033[0m\]" | |
| function ruby_version { | |
| if [[ -f ~/.rvm/bin/rvm-prompt ]]; then | |
| local system=$(~/.rvm/bin/rvm-prompt s) | |
| local interp=$(~/.rvm/bin/rvm-prompt i) | |
| if [[ ! -n $system ]]; then | |
| # Don't show interpreter if it's just MRI |
| #!/bin/sh | |
| # Converts a mysqldump file into a Sqlite 3 compatible file. It also extracts the MySQL `KEY xxxxx` from the | |
| # CREATE block and create them in separate commands _after_ all the INSERTs. | |
| # Awk is choosen because it's fast and portable. You can use gawk, original awk or even the lightning fast mawk. | |
| # The mysqldump file is traversed only once. | |
| # Usage: $ ./mysql2sqlite mysqldump-opts db-name | sqlite3 database.sqlite | |
| # Example: $ ./mysql2sqlite --no-data -u root -pMySecretPassWord myDbase | sqlite3 database.sqlite |
| #! /bin/bash | |
| open $1 -a /Applications/iA\ Writer.app |
| <!doctype html> | |
| <html> | |
| <body> | |
| <header role="banner"> | |
| <a href="/" rel="home">My company</a> | |
| <nav role="navigation"> | |
| <a href="/about">About</a> | |
| <a href="/contact">Contact</a> | |
| </nav> | |
| </header> |
| require 'rubygems' | |
| require 'sinatra' | |
| require 'pony' | |
| require 'haml' | |
| set :haml, {:format => :html5} | |
| set :public, File.dirname(__FILE__) | |
| set :views, File.dirname(__FILE__) | |
| # Create the page class and give it a title of Contact for the layout |
It's pretty easy to do polymorphic associations in Rails: A Picture can belong to either a BlogPost or an Article. But what if you need the relationship the other way around? A Picture, a Text and a Video can belong to an Article, and that article can find all media by calling @article.media
This example shows how to create an ArticleElement join model that handles the polymorphic relationship. To add fields that are common to all polymorphic models, add fields to the join model.
| # app/models/ability.rb | |
| # All front end users are authorized using this class | |
| class Ability | |
| include CanCan::Ability | |
| def initialize(user) | |
| user ||= User.new | |
| can :read, :all |
