Anthony Alayo anthonyalayo

Example of Kustomized Helm Install
(Using Helm's Post Rendering Feature)

Overview: Why would you want to do this?

Background Context:

Question: What is a helm chart?
Answer: helm charts are just templating engines that render generated yaml
- input variables (with a mix of default and override values for those variables)
- get plugged into golang templatized yaml
- and output a wall of text of generated yaml
Community Helm Charts:

Helm Chart Conventions

Coding conventions for Helm Charts. This document is subject to change based on the ongoing Helm best practices discussion

NOTE: Official Best Practices have been updated - refer to the official Helm Chart Best practices

Kubernetes Chart requirements

Adapted from the Official Kubernetes Chart Requirements

📓 Table of Contents 📚 Resources ✉️ Chat

kitsunekko.net jp subtitles

A large repository of japanese subtitles that is updated reasonably often and has a clean design.| The most popular one, you can upload your own subs.| Often have to be retimed.

13 valuable things I learned using CMake

Author : Dua Guillaume
Date : 04-26-2020

Requirement : A first experience with CMake

Intro

As a modern C++ specialist, my job is to focus on software development, from a performance and quality perspective.

Handling Errors

Express.js makes it a breeze to handle errors in your routes.

Express lets you centralizes your error-handling through middleware.

Let's look at patterns for how to get the most out of your error-handling.

First, our error-handling middleware looks like this:

2021 Update: Easiest option is Justin's repo and image

Just run this from your Mac terminal and it'll drop you in a container with full permissions on the Docker VM. This also works for Docker for Windows for getting in Moby Linux VM (doesn't work for Windows Containers).

docker run -it --rm --privileged --pid=host justincormack/nsenter1

more info: https://github.com/justincormack/nsenter1

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

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

	# put this file in the top source dir (CMAKE_SOURCE_DIR)
	# see: https://cmake.org/cmake/help/latest/module/CMakeGraphVizOptions.html

	set(GRAPHVIZ_EXTERNAL_LIBS FALSE)
	# only dependencies between libraries
	set(GRAPHVIZ_EXECUTABLES FALSE)

	set(LIBFOO_TAR_HEADERS
	"${CMAKE_CURRENT_BINARY_DIR}/include/foo/foo.h"
	"${CMAKE_CURRENT_BINARY_DIR}/include/foo/foo_utils.h"
	)

	add_custom_command(OUTPUT ${LIBFOO_TAR_HEADERS}
	COMMAND ${CMAKE_COMMAND} -E tar xzf "${CMAKE_CURRENT_SOURCE_DIR}/libfoo/foo.tar"
	COMMAND ${CMAKE_COMMAND} -E touch ${LIBFOO_TAR_HEADERS}
	WORKING_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/include/foo"
	DEPENDS "${CMAKE_CURRENT_SOURCE_DIR}/libfoo/foo.tar"