Benjamin Dos Santos bdossantos

GitHub Pages "Normal" Setup for User & Organization Pages

Let’s say your GitHub username is “alice”. If you create a GitHub repository named alice.github.com, commit a file named index.html into the master branch, and push it to GitHub, then this file will be automatically published to http://alice.github.com/... The same works for organizations.

Read more here: http://pages.github.com/

However... the downside of this is that anyone that forks this repo won't get it as a GitHub Pages repo when they are working on it... because they have a different GitHub "username" (or "organisation name").

So the trick is to not use a master branch as the documentation tells you... rather, use a gh-pages branch, as you would for your other "Project Pages".

[PLUGIN NAME] Plugin

[ONE LINE DESCRIPTION OF PROJECT]

Background

[A PARAGRAPH DESCRIBING WHY YOU BUILT THIS]

[ANOTHER PARAGRAPH DESCRIBING YOUR IMPETUS FOR RELEASING THIS]

	# Clone rbenv into ~/.rbenv
	git clone [email protected]:sstephenson/rbenv.git ~/.rbenv

	# Add rbenv to your PATH
	# NOTE: rbenv is NOT compatible with rvm, so you'll need to
	# remove rvm from your profile if it's present. (This is because
	# rvm overrides the `gem` command.)
	echo 'export PATH="$HOME/.rbenv/bin:$HOME/.rbenv/shims:$PATH"' >> ~/.bash_profile
	exec $SHELL

	#!/usr/bin/env python
	# -- coding: utf-8 --
	"""nginx_error_rate -- Munin plugin to report the error rate in an access log.

	The access log defaults to `/var/log/nginx/access.log`. This may be
	customized with the following stanza in your munin plugin conf:

	[nginx_error_rate]
	env.access_log /path/to/access.log
	"""

	<!-- Place this tag just before your close body tag and NOT in your <head> -->
	<script>
	(function(d, t) {
	var g = d.createElement(t),
	s = d.getElementsByTagName(t)[0];
	g.async = true;
	g.src = 'https://apis.google.com/js/plusone.js';
	s.parentNode.insertBefore(g, s);
	})(document, 'script');
	</script>

	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<title>CSS responsive images</title>
	<style>
	/* Doesn't stop original source image being
	downloaded too */

	@media (min-device-width:600px) {

	###############################################################################
	## Includes
	###############################################################################
	##
	## It is possible to include additional configuration parts from other files or
	## directories.
	#
	# include /etc/monit.d/*
	#
	#

	upstream php-fpm {
	server unix:/var/run/php5-fpm.sock;
	}

	server {
	listen 80;
	server_name www.example.com;
	rewrite ^ http://example.com$request_uri?;
	}

	// early experiments with node had mysterious double requests
	// turned out these were for the stoopid favicon
	// here's how to short-circuit those requests
	// and stop seeing 404 errors in your client console

	var http = require('http');

	http.createServer(function (q, r) {

	// control for favicon

	#!/bin/sh
	# ------------------------------------------------------------------------------
	# SOME INFOS : fairly standard (debian) init script.
	# Note that node doesn't create a PID file (hence --make-pidfile)
	# has to be run in the background (hence --background)
	# and NOT as root (hence --chuid)
	#
	# MORE INFOS : INIT SCRIPT http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit
	# INIT-INFO RULES http://wiki.debian.org/LSBInitScripts
	# INSTALL/REMOVE http://www.debian-administration.org/articles/28