Stefan Junker steveej

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

query
mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

This post is deprecated!

Its contents have been moved to the NixOS wiki here, where they are being kept up to date. Please follow the instructions there instead!

The original post is below for posterity.

Functional, Reactive, and Distributed Systems Bibliography

Books

CQRS Journey: Free ebook from Microsoft (Print book available for purchase)
Functional and Reactive Domain Modeling: A high level overview of how to build up domain models using free monads and interpreters.
Reactive Microservices Architecture: Free booklet from Lagom and O'Reilly
Reactive Messaging Patterns with the Actor Model: Applications and Integration in Scala and Akka
Domain-Driven Design: Tackling Complexity in the Heart of Software

using rust with rr

rr is a great debugging tool. it records a trace of a program's execution, as well as the results of any syscalls it executes, so that you can "rewind" while you debug, and get deterministic forward and reverse instrumented playback. it works with rust, but by default if you try it out, it could be pretty ugly when you inspect variables. if this bothers you, configure gdb to use a rust pretty-printer

rr is probably in your system's package manager.

usage

You don't need a blockchain.

If you're reading this, you probably suggested to somebody that a particular technical problem could be solved with a blockchain.

Blockchains aren't a desirable thing; they're defined by having trustless consensus, which necessarily has to involve some form of costly signaling to work; that's what prevents attacks like sybil attacks.

In other words: blockchains must be expensive to operate, to work effectively. This makes it a last-resort solution, when you truly have no other options available for solving your problem; in almost every case you want a cheaper and less complex solution than a blockchain.

In particular, if your usecase is commercial, then you do not need or want trustless consensus. This especially includes usecases like supply chain tracking, ticketing, and so on. The whole *p

walkthrough: buildah on knative

The buildah utility is a versitile container build tool that does not require a daemon (everything is direct invocation). See my "deep dive" for a few hands on use-cases.

Recently knative was announced. It is a project to enable the kubernetes primitives needed to build a functions-as-a-service. There are a plumbing services needed around this use-case, "build" is one of them. Building containers is largely an indepenent goal and story of "serverless" or "FaaS", but I get why they are grouped together.

	This document describes about installation and configuration of IPMI simulator.
	We need: qemu-kvm, OpenIPMI, OpenIPMI-tools
	1) Install the qemu-kvm. We need the qemu, which have the IPMI pacthes.
	Use the source https://github.com/cminyard/qemu/tree/stable-2.2-ipmi
	./configure, make and make install

	2) Download the OpenIPMI libraries, from http://sourceforge.net/projects/openipmi/
	Follow the process documented in lanserv/README.vm
	./configure --prefix=/opt/openipmi/usr --sysconfdir=/opt/openipmi/etc \
	--with-perlinstall=/opt/openipmi/usr/lib/perl \

	{
	pkgs ? import <nixpkgs> {},
	internalDomain ? "cluster.local",
	externalDomain ? "<domain_name>",
	serviceClusterIp ? "10.0.0.1"
	}:
	let
	runWithCFSSL = name: cmd:
	builtins.fromJSON (builtins.readFile (
	pkgs.runCommand "${name}-cfss.json" {