Jakob Lorz jakoblorz

WARNING: If you're reading this in 2021 or later, you're likely better served by reading:

(This gist was created in 2013 and targeted the legacy GOPATH mode.)

$ ssh -A vm
$ git config --global url."git@github.com:".insteadOf "https://github.com/"

Simple Git Workflow For Continuous Delivery

Workflow guidelines:

master branch is always production-ready, deployable, 100% green test suite
New development is done on feature branches, with frequent rebasing onto master
Clean commit history by preferring to rebase instead of merge (git pull is configured to automatically rebase)

Workflow

CI with Travis, GitHub Releases API and gh-pages

When hosting a project on GitHub, it's likely you'll want to use GitHub Pages to host a public web site with examples, instructions, etc. If you're not using a continuous integration service like Travis, keeping your gh-pages site up to date requires continuous wrangling.

The steps below outline how to use Travis CI with GitHub Releases and GitHub Pages to create a "1-button" deployment workflow. After testing and running a release build, Travis will upload your release assets to GitHub. It will also push a new version of your public facing site to GitHub Pages.

Organize your project

Let's assume you are hosting a JavaScript project that will offer a single JavaScript file as a release asset. It's likely you'll organize your files like this.

How to Aggregate Gazillion Geo Data for Instant Display (WIP)

(Cleaning up for CQL3 interface using DataStax driver)

Let's say you have a large amount of Geo data. Let's say it's GPS data from thousands of autonomous drones mapping geo areas around the country. Or it could be something boring like a truck fleet positional information.

Either way, it's lots and lots of data in the form of Coordinates associated with some kind of value. And now that you have gazillion geo data, you want to visualize this data. A heatmap, perhaps.

If the data is relatively small as in up to a few hundred K's, you can simply put this into a heatmap and it'll probably work.

	CREATE TABLE adressen.land
	(
	isocode_2 character(2) not null, -- ISO 3166 ALPHA-2
	isocode_3 character(3) not null, -- ISO 3166 ALPHA-3
	name character varying not null, -- deutscher Name des Landes (international besser via ISO-Code ankoppeln!) // German name of the country
	vorwahl integer default null, -- internationale Vorwahl // international phone code
	null_bei_vorwahl boolean default FALSE, -- muss man die Null der Ortsvorwahl auch nach der internationalen Vorwahl wählen? // must one dial zero between international and local phone code?
	vorwahl_lokal boolean default FALSE, -- muss man vor Ort die Vorwahl wählen? // must one dial the local phone code also locally?
	tld character varying default NULL, -- Top Level Domain
	kfz character varying default NULL, -- KFZ-Kennzeichen // car code

	// this will find all files ending with _test.js and run them with Mocha. Put this in your package.json


	"scripts": {
	"test": "find ./tests -name '*_test.js' \| xargs mocha -R spec"
	},

	#!/usr/bin/python

	#=======================================
	# Configure Options here
	#=======================================

	username = "TU-ID hier"
	password = "Passwort hier"

	firstYear = 2012

	package main

	import (
	"bytes"
	"fmt"
	"io"
	"log"
	"mime/multipart"
	"net/http"
	"os"

	/*
	In the node.js intro tutorial (http://nodejs.org/), they show a basic tcp
	server, but for some reason omit a client connecting to it. I added an
	example at the bottom.

	Save the following server in example.js:
	*/

	var net = require('net');

	FROM ubuntu

	RUN apt-get update
	RUN apt-get install -y socat

	VOLUME /foo

	CMD socat UNIX-LISTEN:/foo/bar.sock -