Kien Nguyen-Tuan ntk148v

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

IRC Reference

by xero updated 10.29.24

	#!/usr/bin/python
	# -- coding: utf-8 --

	import numpy as np
	import matplotlib.pyplot as plt


	class RidgeRegressor(object):
	"""
	Linear Least Squares Regression with Tikhonov regularization.

	#!/usr/bin/env python
	# coding: utf-8

	import argparse
	import os
	import sys
	import time
	import atexit
	import logging
	import signal

	#!/usr/bin/python
	# -- coding: utf-8 --
	"""
	Zabbix SMTP Alert script for gmail.
	"""

	import sys
	import smtplib
	from email.MIMEText import MIMEText
	from email.Header import Header

	#!/usr/bin/env python
	# http://stackoverflow.com/questions/14180179/eventlet-spawn-doesnt-work-as-expected/14180227#14180227

	from flask import Flask
	import time
	import eventlet

	eventlet.monkey_patch()

	app = Flask(__name__)

	#! /usr/bin/python
	# Dispatch - synchronize two folders

	import os
	import filecmp
	import shutil
	from stat import *

	class Dispatch:
	''' This class represents a synchronization object '''

	"""
	Settings for root logger.
	Log messages will be printed to console and also to log file (rotated, with
	specified size). All log messages from used libraries will be also handled.

	Three approaches for defining logging settings are used:
	1. using logging classes directly (py25+, py30+)
	2. using fileConfig (py26+, py30+)
	3. using dictConfig (py27+, py32+)
	Choose any variant as you like, but keep in mind python versions, that

	#!/bin/bash
	# Sometimes you need to move your existing git repository
	# to a new remote repository (/new remote origin).
	# Here are a simple and quick steps that does exactly this.
	#
	# Let's assume we call "old repo" the repository you wish
	# to move, and "new repo" the one you wish to move to.
	#
	### Step 1. Make sure you have a local copy of all "old repo"
	### branches and tags.

	#!/bin/bash

	set -ex

	#
	# The network interface that will be used by OpenStack services.
	# The IP address of this interface will be used in the service
	# catalog for admin and internal endpoints.
	#
	net_interface=eth0