Jamie Barton notrab

Friendly URLs

By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:

/people/6

But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.

Step 0:

Get Homebrew installed on your mac if you don't already have it

Step 1:

Install highlight. "brew install highlight". (This brings down Lua and Boost as well)

Step 2:

My issues with Modules

In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.

A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.

You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.

class Article &lt; ActiveRecord::Base

Deploying a subfolder to GitHub Pages

Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.

For the sake of this example, let’s pretend the subfolder containing your site is named dist.

Step 1

Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).

Deploying Ember on Heroku using Yeoman

I'm going to assume here that you have an ember application ready that you want to deploy.
Install Generator Heroku using the steps there, and don't forget to add the block of code to your gruntfile.js. You should find the copy tag already there, just append to it
The run grunt build command to generate the /dist folder. That will complie everything and generate your web-app
If you want you can test it using grunt server:dist
Now go to /dist folder
Create a heroku app heroku create
Commit everything in the dist folder (Don't go up to your root direcotry, you want to commit update to heroku) I used github to add local repo and manage everything from there.

	echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
	. ~/.bashrc
	mkdir ~/local
	mkdir ~/node-latest-install
	cd ~/node-latest-install
	curl http://nodejs.org/dist/node-latest.tar.gz \| tar xz --strip-components=1
	./configure --prefix=~/local
	make install # ok, fine, this step probably takes more than 30 seconds...
	curl https://www.npmjs.org/install.sh \| sh

	var gulp = require('gulp'),
	sass = require('gulp-sass'),
	browserify = require('gulp-browserify'),
	concat = require('gulp-concat'),
	embedlr = require('gulp-embedlr'),
	refresh = require('gulp-livereload'),
	lrserver = require('tiny-lr')(),
	express = require('express'),
	livereload = require('connect-livereload')
	livereloadport = 35729,

	# Created by http://www.gitignore.io

	### Xcode ###
	build
	.xcodeproj/
	!*.xcodeproj/project.pbxproj
	!*.xcworkspace/contents.xcworkspacedata


	### Objective-C ###

	// Node.js proxy server for CORS requests with single page, no-backend apps.
	//
	// Instructions:
	// 1) Place file into your app directory
	// 2a) If you don't have a package.json file in this directory, run "npm init" first
	// 2b) Run "npm install --save express request query-string"
	// 3) Run server with "node server.js"
	// 4) Configure Express to use whatever folder you want to serve your site out of.
	// By default, this will run out of whatever folder you have your server.js in,
	// but you shouldn't do this since it'll make everything in this folder accessible,


	gem 'omniauth'
	gem 'omniauth-facebook'
	gem 'clearance'