devzakir

GitHub allows you to attach a deploy key to any of your repositories. However, each repo must have its own unique key. If you’re deploying multiple GitHub repos on a single machine, that means you’ll need to set up multiple ssh keys for that machine. The easiest way to achieve this is to leverage ssh’s host config. If you have mygithubuser/repo1 and mygithubuser/repo2 that you want to deploy on a single machine, first create an rsa key pair for each repo:

ssh-keygen -t rsa -f ~/.ssh/repo1_rsa -C "repo1 deploy"
ssh-keygen -t rsa -f ~/.ssh/repo2_rsa -C "repo2 deploy"

Cat the public keys and copy+paste them into each repo’s respective GitHub deploy key:

blvz

#!/usr/bin/env bash

read -r -d '' usage << EOM
Usage:

  gh-deploy-clone user/repo [ENVIRONMENT]
EOM

[ -z "$1" ] && echo && echo "$usage" && echo && exit 1

cobyism

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