Michael Wolfenden michael-wolfenden

Windows Containers notes

Published ports from Windows Containers aren't accessible on the container host (they are remotely). Use Container IP locally:
- docker inspect --format '{{ .NetworkSettings.Networks.nat.IPAddress }}' <container>
- Docs explaining this
- GH Issue tracking fixes
  - host's IP on host does work now in Creator's Update: "as well as having direct access to the container using the Host IP and exposed port." - https://blogs.technet.microsoft.com/virtualization/2017/04/13/whats-new-in-hyper-v-for-the-windows-10-creators-update/
  - localhost on host doesn't work yet
Troubleshooting & Logs - Docker docs: https://docs.docker.com/docker-for-windows/troubleshoot/#docker-knowledge-hub

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

SignalR generates a hub for each method invoke ie onConnected, onDisconnect or any other methods on the hub. Autofac.SignalR all hub dependencies are resolved from the root container making them singletons.

I did find another solutions https://github.com/lethek/SignalR.Extras.Autofac but this required inheriting from a special lifetimehub, retro fitting this into an large existing solution would take a lot of work an re-testing.

The solutions below allows you to scope all dependencies per hub instance.

Install-Package Autofac.SignalR
Install-Package Castle.Core

ServiceWorker for github pages

This is a ServiceWorker template to turn small github pages into offline ready app.

Why ?

Whenever I make small tools & toys, I create github repo and make a demo page using github pages (like this one).
Often these "apps" are just an index.html file with all the nessesary CSS and JavaScript in it (or maybe 2-3 html/css/js files). I wanted to cache these files so that I can access my tools offline as well.

Notes

Make sure your github pages have HTTPS enforced, you can check Settings > GitHub Pages > Enforce HTTPS of your repository.

We subscribe to the Git Featrue Branch workflow, briefly described in that link.

In practice, it works as follows:

FEATURE DEVELOPMENT

Steps to Follow:

Start with an updated local development branch -- by checking out the dev branch and pulling changes:
git checkout development
git pull origin development

Goal: run a simple NodeJS application inside a Docker container

Subgoal: give it access to local files.

docker run -it --rm --name example -v "$PWD":/usr/src/app -w /usr/src/app node:5-slim node index.js

output:

	const webpack = require('webpack')
	const fs = require('fs')

	// NODE_ENV
	const nodeEnv = process.env.NODE_ENV \|\| 'development'
	const isProd = nodeEnv === 'production'

	module.exports = (options) => {
	let entryFile, outputPath, isClient, isServer

	import { h, Component } from 'preact';


	/** Creates a new store, which is a tiny evented state container.
	* @example
	* let store = createStore();
	* store.subscribe( state => console.log(state) );
	* store.setState({ a: 'b' }); // logs { a: 'b' }
	* store.setState({ c: 'd' }); // logs { c: 'd' }
	*/

	#!/bin/sh
	# Benjamin Collins <[email protected]>
	# Requires GNU readlink (get on macOS with `brew install coreutils`)
	READLINK=${READLINK:-readlink}

	cliPath=$(which dotnet)
	netDir=$(dirname $($READLINK -f $cliPath))

	ls -1 "$netDir/sdk"

	public Assembly[] GetAssemblies()
	{
	var assemblies = new List<Assembly>();
	foreach(ProcessModule module in Process.GetCurrentProcess().Modules)
	{
	try
	{
	var assemblyName = AssemblyLoadContext.GetAssemblyName(module.FileName);
	var assembly = Assembly.Load(assemblyName);
	assemblies.Add(assembly);