Morten Linderud Foxboron

About

This is a local copy of the commands from:

This guide serves as a reference of collected information necessary for strict management of PGP keys. This includes keeping a master key that always remains

a simple git branching model

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

The gist

My Darktable Workflow

Basic workflow

Copy a film roll (a directory of RAW images) into a directory on the machine running Darktable.
Import the film roll into Darktable.
Review the images using lighttable mode and remove any images that are beyond repair.
Take a snapshot of the image so we can do a before and after comparison.
Adjust the white balance.
Exposure compensation and recovery.

Prebase

git-prebase improves on 'git rebase -i' by adding information per commit regarding which files it touched.

Each file gets an alpha-numeric identifier at a particular column, a list of which appears below the commit list. (The identifiers wrap around after the 62nd file)
Commits can be moved up and down safely (without conflicts) as long as their columns don't clash (they did not touch the same file).

Installation

Add the executable to your path and git will automatically expose it as

Make sure you've installed hy or put it in requirements.txt
Put hy.py in management/commands/hy.py

  ./manage.py hy
  hy 0.11.0 using CPython(default) 2.7.6 on Linux
  => (import [yourapp [settings]])
  => settings.DEBUG
  True

Promises reading list

This is a list of examples and articles, in roughly the order you should follow them, to show and explain how promises work and why you should use them. I'll probably add more things to this list over time.

This list primarily focuses on Bluebird, but the basic functionality should also work in ES6 Promises, and some examples are included on how to replicate Bluebird functionality with ES6 promises. You should still use Bluebird where possible, though - they are faster, less error-prone, and have more utilities.

I'm available for tutoring and code review :)

You may reuse all gists for any purpose under the WTFPL / CC0 (whichever you prefer).

"How do I get started with Node?" is a commonly heard question in #Node.js. This gist is an attempt to compile some of the answers to that question. It's a perpetual work-in-progress.

And if this list didn't quite answer your questions, I'm available for tutoring and code review! A donation is also welcome :)

Setting expectations

Before you get started learning about JavaScript and Node.js, there's one very important article you need to read: Teach Yourself Programming in Ten Years.

Understand that it's going to take time to learn Node.js, just like it would take time to learn any other specialized topic - and that you're not going to learn effectively just by reading things, or following tutorials or courses. _Get out there and build things!

	# Copy the following and place it a file called Leiningen.sublime-build in the Sublime user packages folder (~/.config/sublime-text-2/Packages/User on Linux).
	# Select this as the build system for the project using Tools/Build System/Leiningen.
	# You can then bring up the Sublime Command Palette (ctrl+shift+P on Windows/Linux) and issue any of the commands # (build, documentation, clean, run, test, etc). By default, build is bound to ctrl+b and run to ctrl+shift+b.


	{
	"cmd": ["lein", "compile", ":all"],
	"working_dir": "$file",
	"variants": [
	{ "cmd": ["lein", "marg", "-m", "-d", "docs"],

	# Gist is stupid and doesn't seem to allow manual selection of syntax highlighting; .sh extension is used for increased readability.

	# This is only a guide to show the required steps for successful UEFI + GRUB2 installation
	# Many of the choices are examples or assumptions; don't blindly type shit into your machine
	# until/unless you at least read the comments around each command
	#
	# These steps assume you've booted in UEFI mode by preparing your USB stick per these instructions:
	# https://wiki.archlinux.org/index.php/UEFI#Archiso
	#
	# If you're using an actual CD burned from the official Arch ISO, just make sure you've booted it in UEFI mode

	var gulp = require('gulp');
	var sourcemaps = require('gulp-sourcemaps');
	var source = require('vinyl-source-stream');
	var buffer = require('vinyl-buffer');
	var browserify = require('browserify');
	var watchify = require('watchify');
	var babel = require('babelify');

	function compile(watch) {
	var bundler = watchify(browserify('./src/index.js', { debug: true }).transform(babel));