Ahsan Nabi Dar ahsandar

Let's Encrypt on Ubuntu 14.04, nginx with webroot auth

This document details how I setup LE on my server. Firstly, install the client as described on http://letsencrypt.readthedocs.org/en/latest/using.html and make sure you can execute it. I put it in /root/letsencrypt.

As it is not possible to change the ports used for the standalone authenticator and I already have a nginx running on port 80/443, I opted to use the webroot method for each of my domains (note that LE does not issue wildcard certificates by design, so you probably want to get a cert for www.example.com and example.com).

Configuration

For this, I placed config files into etc/letsencrypt/configs, named after <domain>.conf. The files are simple:

auth with microservices

Authorization and Authentication are hard. when you only have to implement them once (as you do within a monolith) instead of over and over again, it makes the developer happy :-), and maybe leads to less implementation failures.

When you have a bunch of microservices, this is something that has to be considered.

Implement it once or in every microservice, or something in between?

emacs --daemon to run in the background. emacsclient.emacs24 <filename/dirname> to open in terminal

NOTE: "M-m and SPC can be used interchangeably".

Undo - C-/
Redo - C-?
Change case: 1. Camel Case : M-c 2. Upper Case : M-u

Lower Case : M-l

Server scripts

This is the source for the scripts discussed in https://robots.thoughtbot.com/improving-user-experience-with-shell-scripts

Both scripts are in the bin/ directory of the repo that contains all the markdown documents for blog posts. Users run bin/server and everything is automatically set up for them to view a local preview of the blog. bin/server-setup is a dependency of bin/server and is never run directly by users.

Maitre-d is the name of the "blog engine" discussed in the article.

Mac Homebrew (RVM/MySQL/Redis) setup

Follow the steps below to setup a local development environment:

XQuartz

Recommended to download latest XQuartz

iTerm2

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

	upstream myapp {
	server 127.0.0.1:8081;
	}

	limit_req_zone $binary_remote_addr zone=login:10m rate=1r/s;

	server {
	listen 443 ssl spdy;
	server_name _;

	nginx/
	!nginx/.gitkeep
	!nginx/logs/.gitkeep

	src/

	tmp/

	require 'open-uri'
	require 'zlib'
	require 'yajl'

	# References
	# - https://developers.google.com/bigquery/preparing-data-for-bigquery#dataformats
	# - https://developers.google.com/bigquery/docs/data#nested
	#

	def type(t)

	######################
	#
	# Monkey patch to ActiveRecord to prevent 'implicit' checkouts. Currently tested with Rails 4.0.8, prob
	# should work fine in Rails 4.1 too.
	#
	# If you create a thread yourself, if it uses ActiveRecord objects without
	# explicitly checking out a connection, one will still be checked out implicitly.
	# If it is never checked back in with `ActiveRecord::Base.clear_active_connections!`,
	# then it will be leaked.
	#