Mike Chau mikechau

Disclaimer: Please follow this guide being aware of the fact that I'm not an expert regarding the things outlined below, however I made my best attempt. A few people in IRC confirmed it worked for them and the results looked acceptable.

Attention: After following all the steps run gdk-pixbuf-query-loaders --update-cache as root, this prevents various gdk-related bugs that have been reported in the last few hours. Symptoms are varied, and for Cinnamon the DE fails to start entirely while for XFCE the icon theme seemingly can't be changed anymore etc.

Check the gist's comments for any further tips and instructions, especially if you are running into problems!

Screenshots

Results after following the guide as of 11.01.2017 13:08:

When you use the names property in the CommonsChunkPlugin({}) and pass an array as the value, webpack converts what is seen below:

      new webpack.optimize.CommonsChunkPlugin({
        names: ['app', 'vendor', 'manifest'],  // creating manifest.js 
        minChunks: Infinity
      })

Into:

Installing a Gem on Heroku from a Private GitHub Repo

Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.

Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.

This method does not add your OAuth token to Gemfile.lock. It uses bundle config to store your credentials, and allows you to configure Heroku to use environment variables when deploying.

Generate an OAuth token from GitHub

	#!/usr/bin/env bash

	set -o xtrace -o errexit -o pipefail -o nounset

	########################################################################################
	# CircleCI's current recommendation for roughly serializing a subset
	# of build commands for a given branch
	#
	# circle discussion thread - https://discuss.circleci.com/t/serializing-deployments/153
	# Code from - https://github.com/bellkev/circle-lock-test

	// makeRouteComponent.js
	import { compile } from 'path-to-regexp'
	import { Route } from 'react-router'

	export const makeRouteComponent = config => Comp => {
	Comp.__toPath = compile(config.path)
	return <Route {...config} component={Comp}/>
	}

	export const pathTo = (Comp, params) => (

	// something like:
	<BundleLink to="/profile" onLoadStart={() => {
	// throw a spinner up on the "old" page while we load
	this.setState({ navigating: true })
	}}>Profile</BundleLink>

	<BundleLink to="/dash" prefetch={true}>Dashboard</BundleLink>

	///////////////////////////////////////////////////////
	const BUNDLED_ROUTES = {

	#!/usr/bin/env bash
	set -e

	function usage() {
	set -e
	cat <<EOM
	##### ecs-run #####
	Simple script for running tasks on Amazon Elastic Container Service
	One of the following is required:
	Required arguments:

	import React from 'react';

	const toPromise = (load) => (new Promise((resolve) => (
	load(resolve)
	)));

	class LazilyLoad extends React.Component {

	constructor() {
	super(...arguments);

	// @flow

	// Goal: define a top-level app state like the following. `sources`
	// would be state managed by a redux reducer
	type SourceState = { count: number };
	type AppState = { sources: SourceState};

	// Define a selector that takes a piece of the state, like sources
	// (this is contrived)
	function getNumSources(state: SourceState, x : number) {

	Result: 1
	Items {
	TemplateId: "BADGE_BATTLE_ATTACK_WON"
	Badge {
	BadgeType: BADGE_BATTLE_ATTACK_WON
	BadgeRanks: 4
	Targets: "\nd\350\007"
	}
	}
	Items {