Joseph Bolus josephbolus

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

Description

This template runs my experimental NPM service as part of evaluating if i should stop using my hand crafted nginx reverse proxy. Note change your passwords and don't use the examples bellow :-) )

State Considerations for SWARM

This container has a database, as such I store the data on the gluster volume. I am currenlty using a mount point to store the voume data on glusterfs. I restrict to 1 instance of each container to avoid database corruption from having two instances. Change example usernames and passwords as needed. leave hostname as db (name resolution works fine using the method)

The variable name is ansible_ssh_private_key_file .

One should set it at 'vars' level:

in the inventory file:

myHost ansible_ssh_private_key_file=~/.ssh/mykey1.pem
myOtherHost ansible_ssh_private_key_file=~/.ssh/mykey2.pem

Complete solution for websites hosting

This gist contains example of how you can configure nginx reverse-proxy with autmatic container discovery, SSL certificates generation (using Let's Encrypt) and auto updates.

Features:

Automatically detect new containers and reconfigure nginx reverse-proxy
Automatically generate/update SSL certificates for all specified containers.
Watch for new docker images and update them.
Ban bots and hackers who are trying to bruteforce your website or do anything suspicious.

	#!/bin/bash
	currentAttempt=0
	totalAttempts=10
	delay=15

	while [ $currentAttempt -lt $totalAttempts ]
	do
	currentAttempt=$(( $currentAttempt + 1 ))

	echo "Attempt $currentAttempt of $totalAttempts..."

	# This file contains pin mappings for the Creality "v4.2.7" board. To
	# use this config, during "make menuconfig" select the STM32F103 with
	# a "28KiB bootloader" and serial (on USART1 PA10/PA9) communication.

	# If you prefer a direct serial connection, in "make menuconfig"
	# select "Enable extra low-level configuration options" and select
	# serial (on USART3 PB11/PB10), which is broken out on the 10 pin IDC
	# cable used for the LCD module as follows:
	# 3: Tx, 4: Rx, 9: GND, 10: VCC

	From: http://www.chromium.org/developers/design-documents/network-stack/socks-proxy

	To configure chrome to proxy traffic through the SOCKS v5 proxy server myproxy:8080, launch chrome with these two command-line flags:

	--proxy-server="socks5://myproxy:8080"
	--host-resolver-rules="MAP * 0.0.0.0 , EXCLUDE myproxy"

	The first thing to check when debugging is look at the Proxy tab on about:net-internals, and verify what the effective proxy settings are:
	chrome://net-internals/#proxy

	# Refer to the Caddy docs for more information:
	# https://caddyserver.com/docs/caddyfile

	:80
	reverse_proxy 10.100.100.1:80

	AWS_ACCESS_KEY_ID=
	AWS_SECRET_ACCESS_KEY=
	AWS_HOSTED_ZONE_ID=