Anton Belodedenko ab77

Don't use VPN services.

No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.

Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.

A Russian translation of this article can be found here, contributed by Timur Demin.
A Turkish translation can be found here, contributed by agyild.
There's also this article about VPN services, which is honestly better written (and has more cat pictures!) than my article.

Raspberry Pi VPN Router

This is a quick-and-dirty guide to setting up a Raspberry Pi as a "router on a stick" to PrivateInternetAccess VPN.

Requirements

Install Raspbian Jessie (2016-05-27-raspbian-jessie.img) to your Pi's sdcard.

Use the Raspberry Pi Configuration tool or sudo raspi-config to:

HTTP Streaming (or Chunked vs Store & Forward)

The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.

However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on

Reverse proxy over 3G modem (draft)

We will explain how to configure a cubieboard running debian as a reverese proxy. The modules that will be used are wvdial and autossh

Credits goes to:

1. http://blog.rootshell.be/2015/02/19/my-little-pwnie-box/
2. https://wiki.archlinux.org/index.php/3G_and_GPRS_modems_with_pppd

I needed a way to have my Django ElasticBeanstalk application automatically redirect HTTP requrests to HTTPS. Rick Christianson wrote a post [1] about how to do this by overwriting the wsgi.conf file with one that was slightly modified to support the HTTP to HTTPS redirect.

Building off the shoulders of giants, I wanted to do the same, but not have to keep a copy of the config file in my local source directory. Christianson even points out in his post that if ElasticBeanstalk ever changes it's template for the wsgi.conf file, those updates would not be overwritten and you wouldn't get their benefits. To get around that problem, I used sed to insert the new lines into the wsgi.conf file.

	#!/bin/bash
	# This script should be located on each Jenkins slave, and the jenkins user should have permission to run it with sudo

	# Attempts to cleanly stop and remove all containers, volumes and images.
	docker ps -q \| xargs --no-run-if-empty docker stop
	docker ps -q -a \| xargs --no-run-if-empty docker rm --force --volumes
	docker volume ls -q \| xargs --no-run-if-empty docker volume rm
	docker images -a -q \| xargs --no-run-if-empty docker rmi -f

	# Stops the docker service, unmounts all docker-related mounts, removes the entire docker directory, and starts docker again.

	{
	"AWSEBDockerrunVersion": "1",
	"Image": {
	"Name": "<AWS_ACCOUNT_ID>.dkr.ecr.us-east-1.amazonaws.com/<NAME>:<TAG>",
	"Update": "true"
	},
	"Ports": [
	{
	"ContainerPort": "443"
	}

	#!/bin/bash

	# Creates script output

	# $1 = app to get ENVs from
	# $2 = app to set ENVs to

	resin envs --application $1 \| tail -n +2 \| sed 's/^[0-9]* //gm' \| sed "s/ \+/ '/gm" \| sed "s/$/'/m" \| sed 's/^/resin env add /m' \| sed "s/$/ --application $2/m"

	{
	"Version": "2012-10-17",
	"Statement": [
	{
	"Action": [
	"ec2:Describe*"
	],
	"Effect": "Allow",
	"Resource": "*"
	}