Wilfred Hughes Wilfred

Auto-deploying built products to gh-pages with GitHub Actions

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.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

Kibana 3 against ElasticSearch 1.4 throws an Connection Failed screen. The error text says to set http.cors.allow-origin, but it misses out the important http.cors.enabled: true

Working config:

$ grep cors elasticsearch-1.4.0.Beta1/config/elasticsearch.yml
http.cors.allow-origin: "/.*/"
http.cors.enabled: true

Ref
Ref

THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.

PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!

	#![feature(mpsc_select, box_syntax)]

	use std::io;
	use std::process::Command;
	use std::sync::mpsc::{channel, Receiver, Select};
	use std::string::FromUtf8Error;
	use std::thread::spawn;

	#[derive(Debug)]
	enum PipeError {

	#!/bin/bash
	#
	# Generates client and server certificates used to enable HTTPS
	# remote authentication to a Docker daemon.
	#
	# See http://docs.docker.com/articles/https/
	#
	# To start the Docker Daemon:
	#
	# sudo docker -d \

	module.exports = (robot) ->
	robot.catchAll (msg) ->
	if msg.message.match /// ^#{robot.name}\s ///
	msg.reply "pardon?" # or whatever

	#!/bin/bash

	BLACK=$(tput setaf 0)
	BLUE=$(tput setaf 1)
	GREEN=$(tput setaf 2)
	CYAN=$(tput setaf 3)
	RED=$(tput setaf 4)
	MAGENTA=$(tput setaf 5)
	YELLOW=$(tput setaf 6)
	WHITE=$(tput setaf 7)

	# Template composition with inclusion
	Every template language I have seen provides some mechanism for one template to include another, thus supporting the reuse of repeated elements like headers and footers. The included templates are called partials in Mustache parlance:

	```html
	<!-- home.hbs -->
	<html>
	<body>
	{{> header}}
	<p> HOME </p>
	{{> footer}}

	# Assuming an Ubuntu Docker image
	$ docker run -it <image> /bin/bash