M. Daniel Dyba dyba

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

In Rails 3

NOTE: This post now lives (and kept up to date) on my blog: http://hakunin.com/rails3-load-paths

If you add a dir directly under app/

Do nothing. All files in this dir are eager loaded in production and lazy loaded in development by default.

If you add a dir under app/something/

Hey there, apparently people are still using this Gist from 2013! It's out of date! Consult the Github docs.

Steps for Hosting a Website on GitHub

Create a GitHub account on github.com.
Download either [GitHub for Mac][1] or [GitHub for Windows][2], depending on your operating system. Open the app and log in using the account you just created.
(On Mac): After you login, click advanced and make sure that your name and email are correct. Then, click "Install Command Line Tools", just in case you want to start using the command line later in life.
Create a new repository in your GitHub application. Name it your-username.github.io. The name is very important. Note the folder that GitHub is saving the repository to. Make sure the "Push to GitHub?" box is checked.
Move your website's files into the folder that GitHub just created when you made the repository. IMPORTANT: Your homepage HTML file must be called "index.html", and it must exist in the top-level

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

Screencasting Framework

The following document is a written account of the Code School screencasting framework. It should be used as a reference of the accompanying screencast on the topic.

Why you should care about screencasting?

You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.

Communicating more effectively - At Envy Labs we produce screencasts for our clients all the time. Whether it's demoing a new feature or for a presentation for an invester, they're often much more effective and pleasent than a phone call or screen sharing.

	extern mod std;

	fn is_three(num: int) -> bool {
	num % 3 == 0
	}

	#[test]
	fn test_is_three_with_not_three() {
	if is_three(1) {
	fail ~"One is not three";

	$stack, $draws = [], {}

	def method_missing *args
	return if args[0][/^to_/]
	$stack << args.map { \|a\| a or $stack.pop }
	$draws[$stack.pop(2)[0][0]] = args[1] if args[0] == :<
	end

	class Array
	def +@

	# SSL self signed localhost for rails start to finish, no red warnings.

	# 1) Create your private key (any password will do, we remove it below)

	$ openssl genrsa -des3 -out server.orig.key 2048


	# 2) Remove the password

	$ openssl rsa -in server.orig.key -out server.key

	#
	# PURPOSE:
	# The purpose of this script is to generate a list of commands to delete unused access rules from a
	# Cisco PIX or ASA firewall. This script is appropriate if you use the RedSeal application:
	# http://www.redsealnetworks.com. Currently the results are printed to the screen only.
	#
	# INSTRUCTIONS:
	# When you want to clean up unused rules on a firewall. Use the RedSeal application to run a cleanup:
	# Tools > Manage Device Cleanup (Alt+T, C). When finished, export the results as a CSV file. Don't
	# forget to include the .CSV extension. Run this script and type the name of the file with the