Skip to content

Instantly share code, notes, and snippets.

@openjck
openjck / kuma-vagrant-reset.sh
Last active August 29, 2015 14:02
Take common steps to fix the Kuma development environment. Basically the equivalent of resetting Firefox or unplugging a router. Restarts as much as possible without losing data.
#!/bin/bash
# Configuration
KUMA_ROOT=/path/to/kuma
# Script
# https://www.youtube.com/watch?v=ckIMuvumYrg
pushd .
cd $KUMA_ROOT
vagrant halt
@cobyism
cobyism / gh-pages-deploy.md
Last active April 12, 2025 09:10
Deploy to `gh-pages` from a `dist` folder on the master branch. Useful for use with [yeoman](http://yeoman.io).

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).

High level style in javascript.

Opinions are like assholes, every one has got one.

This one is mine.

Punctuation: who cares?

Punctuation is a bikeshed. Put your semicolons, whitespace, and commas where you like them.

@lancejpollard
lancejpollard / node-folder-structure-options.md
Created November 28, 2011 01:50
What is your folder-structure preference for a large-scale Node.js project?

What is your folder-structure preference for a large-scale Node.js project?

0: Starting from Rails

This is the reference point. All the other options are based off this.

|-- app
|   |-- controllers
|   |   |-- admin