noname chocopowwwa

AWS Service annotations

service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval (in minutes)
service.beta.kubernetes.io/aws-load-balancer-access-log-enabled (true|false)
service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name
service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix
service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags (comma-separated list of key=value)
service.beta.kubernetes.io/aws-load-balancer-backend-protocol (http|https|ssl|tcp)
service.beta.kubernetes.io/aws-load-balancer-connection-draining-enabled (true|false)

Settting up a Container Registry with docker-gitlab

This should be used for new users to getting started with the container registry feature on docker-gitlab.

Requirements

Docker Distribution >= 2.4
Docker GitLab >= 8.8.4 ( #708 must be merged)
TLS certificates because it should be run with https it's not designed to use it without https

Debugging ES6 in VS Code

My current editor of choice for all things related to Javascript and Node is VS Code, which I highly recommend. The other day I needed to hunt down a bug in one of my tests written in ES6, which at time of writing is not fully supported in Node. Shortly after, I found myself down the rabbit hole of debugging in VS Code and realized this isn't as straightforward as I thought initially. This short post summarizes the steps I took to make debugging ES6 in VS Code frictionless.

What doesn't work

My first approach was a launch configuration in launch.json mimicking tape -r babel-register ./path/to/testfile.js with babel configured to create inline sourcemaps in my package.json. The debugging started but breakpoints and stepping through the code in VS Code were a complete mess. Apparently, ad-hoc transpilation via babel-require-hook and inline sourcemaps do not work in VS Code. The same result for attaching (instead of launch) to `babel-node

README

The example below creates a TCP server listening on a stream (i.e. SOCK_STREAM) socket. A similar approach can be followed to create a UDP server on a datagram (i.e. SOCK_DGRAM) socket. See man systemd.socket for details.

An example server

Create an simple echo server at /opt/foo/serve.py.

README

Create a template service file at /etc/systemd/system/secure-tunnel@.service. The template parameter will correspond to the name of target host:

[Unit]
Description=Setup a secure tunnel to %I
After=network.target

	// move_semantics1.rs
	// Make me compile! Scroll down for hints :)

	pub fn main() {
	let vec0 = Vec::new();

	let mut vec1 = fill_vec(vec0);

	println!("{} has length {} content `{:?}`", "vec1", vec1.len(), vec1);

	From 63db7e5ce57d2c62b89de8bcb2bf7e03d153e600 Mon Sep 17 00:00:00 2001
	From: Aidan Harris <mail@aidanharris.io>
	Date: Mon, 8 May 2017 07:38:55 +0100
	Subject: [PATCH 1/1] Hacks and Bug Fixes

	* Added python-raven to dependencies along with python-setuptools as this is a runtime dependency not just a makedependency.
	* Patched the requirements.txt with sed so that gitfs doesn't complain about the newer versions of python packages. I don't know if this has any adverse side effects but seems to be working so far.
	* Added a .install file that creates the '/var/lib/gitfs' directory, chowns it as 'root:user' with 775 permissions so that gitfs can be used by regular users (provided 'user_allow_other' is uncommented in /etc/fuse.conf)
	---
	.SRCINFO \| 6 +++---

	// For all the confusing Prometheus configuration and
	// regular expressions,
	// explained in examples.


	// Remember, there are default values for each item if it's missing.
	// regex is (.*),
	// replacement is $1,
	// separator is ;
	// ,and action is replace

	#!/usr/bin/env bash

	echo ">>> Installing Mailhog"

	# Download binary from github
	wget --quiet -O ~/mailhog https://github.com/mailhog/MailHog/releases/download/v1.0.0/MailHog_linux_amd64

	# Make it executable
	chmod +x ~/mailhog