Bao Nguyen sysbot

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.

ffmpeg for dummies

Links:

https://trac.ffmpeg.org/wiki/StreamingGuide

https://ffmpeg.org/ffmpeg-devices.html

http://www.ffmpeg.org/ffmpeg-protocols.html#toc-rtp

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

Useful Spacemacs commands

SPC q q - quit
SPC w / - split window vertically
SPC w - - split window horizontally
SPC 1 - switch to window 1
SPC 2 - switch to window 2
SPC w c - delete current window
SPC TAB - switch to previous buffer
SPC b b - switch buffers

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying

	#
	# Some state file...
	#
	{% for site, args in pillar.get('sites', {}).items() %}
	/etc/nginx/sites-available/{{ site }}:
	file.managed:
	- source: salt://nginx/files/site.conf.jinja
	- template: jinja
	- context:
	site: {{ site }}

	zsock_t *radio = zsock_new_radio ("inproc://zframe-test-radio");
	zsock_t *dish = zsock_new_dish ("inproc://zframe-test-radio");

	// Use following for multicast
	// zsock_t *radio = zsock_new_radio ("udp://239.0.0.1:55555");
	// zsock_t *dish = zsock_new_dish ("udp://239.0.0.1:55555");

	// Join to group
	rc = zsock_join (dish, "World");
	assert (rc == 0);