Rodrigo Espinoza rodrigoespinozadev

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:

Terminology

View: Also called a "template", a file that contains markup (like HTML) and optionally additional instructions on how to generate snippets of HTML, such as text interpolation, loops, conditionals, includes, and so on.
View engine: Also called a "template library" or "templater", ie. a library that implements view functionality, and potentially also a custom language for specifying it (like Pug does).
HTML templater: A template library that's designed specifically for generating HTML. It understands document structure and thus can provide useful advanced tools like mixins, as well as more secure output escaping (since it can determine the right escaping approach from the context in which a value is used), but it also means that the templater is not useful for anything other than HTML.
String-based templater: A template library that implements templating logic, but that has no understanding of the content it is generating - it simply concatenates together strings, potenti

	/* This is a small sampling of the various approaches to media queries. The
	point is: they're all over the board. Part of the "issue" (if you can call
	it that) may be due to the intended audience of each site/framework. Another
	may be that it's really difficult to test for a lot of different devices.
	Regardless, it would be really nice if there was standard baseline that
	could be used as a starting point for maximum compatibility and coverage. */

	/* ==========================================================================
	Frameworks
	========================================================================== */

	<?php
	//Automatically login a single WordPress user upon arrival to a specific page.
	//Redirect to home page once logged in and prevent viewing of the login page.
	//Tested with WP 3.9.1. Used in functions.php
	//Updated 2014-07-18 to resolve WP_DEBUG notice: "get_userdatabylogin is deprecated since version 3.3! Use get_user_by('login') instead."
	//From http://tourkick.com/2014/wordpress-demo-multisite-db-reset/

	function auto_login() {
	//change these 2 items
	$loginpageid = '1234'; //Page ID of your login page

	window.resize = (function () {
	'use strict';

	function Resize() {}

	Resize.prototype = {
	init: function(outputQuality) {
	this.outputQuality = (outputQuality === 'undefined' ? 0.8 : outputQuality);
	},

	curl -i -H 'Content-type: application/json' -H 'Authorization: key=<your_server_key>' -XPOST https://fcm.googleapis.com/fcm/send -d '{
	"registration_ids":["registration_ids", "of the", "target", "devices as array"],
	"notification": {
	"title":"Title of your notification",
	"body":"content of your notification"
	},
	"data": {
	"key1" : "value1",
	"key2" : "value2",
	"key3" : 23.56565,

	#for not running docker, use save:
	docker save <dockernameortag> \| gzip > mycontainer.tgz

	#for running or paused docker, use export:
	docker export <dockernameortag> \| gzip > mycontainer.tgz

	#load
	gunzip -c mycontainer.tgz \| docker load

	import dateMixin from './mixins/date';

	// Globally
	Vue.mixin(dateMixin);

	<?php
	/*
	* Mysql database class - only one connection alowed
	*/
	<?php

	class DB {
	private $connection;
	private static $_instance;

	import Sequelize from 'sequelize'
	import bcrypt from 'bcrypt-nodejs'
	import connection from '../config/db'

	require('sequelize-isunique-validator')(Sequelize)

	let User = connection.define('user', {
	firstName: {
	type: Sequelize.STRING(50),
	allowNull: false,