Roman Kiselenko roman-kiselenko

This document has moved!

It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.

Running NGINX and CertBot Containers on the Same Host

The Problem

A lot of people run into the problem of running Let's Encrypt's CertBot Tool and an NGINX on the same container host. A big part of this has to do with CertBot needing either port 80 or 443 open for the tool to work as intended. This tends to conflict with NGINX as most people usually use port 80 (HTTP) or 443 (HTTPS) for their reverse proxy. Section 1 outlines how to configure NGINX to get this to work, and Section 2 is the Docker command to run CertBot.

1. NGINX Configuration

I use Docker Compose (docker-compose) for my NGINX server. My docker-compose.yml file looks something like this:

INTRO

Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".

Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).

Let's dig in:

	package main

	import (
	"bytes"
	"compress/gzip"
	"database/sql/driver"
	"errors"
	"fmt"
	"github.com/jmoiron/sqlx"
	_ "github.com/mattn/go-sqlite3"

	require "diffbench"
	require 'perftools'
	require "bundler"
	Bundler.require
	$:.unshift "../railties/lib"
	$:.unshift "../activesupport/lib"
	$:.unshift "../activemodel/lib"
	$:.unshift "../activerecord/lib"
	require "active_record"
	require 'rails'

	/* eslint-disable no-console */
	import _ from 'underscore';

	/*
	Drop this mixin into a component that wastes time according to Perf.getWastedTime() to find
	out what state/props should be preserved. Once it says "Update avoidable!" for {state, props},
	you should be able to drop in React.addons.PureRenderMixin

	React.createClass {
	mixins: [WhyDidYouUpdateMixin]