Jakub Gruszecki ditrytus

Auto-deploying built products to gh-pages with Travis

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

Create a compile script

You want a script that does a local compile to e.g. an out/ directory. Let's call this compile.sh for our purposes, but for your project it might be npm build or gulp make-docs or anything similar.

The out/ directory should contain everything you want deployed to gh-pages. That almost always includes an index.html.

	;SMBDIS.ASM - A COMPREHENSIVE SUPER MARIO BROS. DISASSEMBLY
	;by doppelganger ([email protected])

	;This file is provided for your own use as-is. It will require the character rom data
	;and an iNES file header to get it to work.

	;There are so many people I have to thank for this, that taking all the credit for
	;myself would be an unforgivable act of arrogance. Without their help this would
	;probably not be possible. So I thank all the peeps in the nesdev scene whose insight into
	;the 6502 and the NES helped me learn how it works (you guys know who you are, there's no

	CLUSTER_NAME='dev-adamg'

	nodegroup_stack=$(
	eksctl utils describe-stacks --cluster $CLUSTER_NAME --color false \| \
	awk '/StackName: "eksctl-'"${CLUSTER_NAME}"'-nodegroup.*"/ { print $2 }' \| \
	sed -e 's/[",]//g;s/\s\+//g'
	)

	nodegroup_role=$(
	aws cloudformation describe-stack-events \