Matthias Pigulla mpdude

Brokkolinudeln mit Ei aus dem Wok (2 Portionen)

Zutaten

125g Mie-Nudeln oder Wok-Nudeln
250g Brokkolie
2 Knoblauchzehen
30g Mandeln
3 Eier
2 Tl Sambal Oelek
1 El Zitronensaft
3 El Sojasauce

Description

This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.

The script is here:

#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"

Results

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

VMware ESXi includes a built in VNC server that can be used to access a VMs console for manipulation via automated tools (e.g., veewee) or by users on platforms where the vSphere Client is not supported. In ESXi 5.x, the built-in firewall does not allow VNC traffic to be received by the VNC server, even when an individual VM is configured to support this configuration. To complete this activity, the firewall has to be modified to allow the appropriate ports.

The below script can be run via the ESXi command line to setup the firewall rules necessary to run VNC. A few items to note:

Scripts assumes the firewall rules file is the default provided as by 5.0.0 update 2 build 914586 and/or 5.1.0 build 799733 (may work in other versions)
In order to persist settings after a reboot, it is necessary to copy the firewall settings to either a specific datastore mapped to the host, or the local persistent storage linked under the /store directory. Further, the either the /etc/rc.local (ESXi 5.0) or `/etc/rc.local

	#!/bin/bash
	# Script to use custom ssh keys for various git repositories
	# Run without arguments to get usage info.
	#
	# How it works:
	# When used with SSH, git sends the path to the repository in the SSH command.
	# @see: https://github.com/git/git/blob/e870325/connect.c#L1268
	# We extract this info and search for a key with the name.
	# Based on the source, this seems to be used format since v2.0 at least.
	# @see: https://github.com/git/git/commit/a2036d7

	parameters:
	env(SECRETS_FILE): .secrets.php

	services:
	# default configuration for services in this file
	_defaults:
	autowire: true # Automatically injects dependencies in your services.
	autoconfigure: true # Automatically registers your services as commands, event subscribers, etc.
	bind:
	$someSecret: '%env(key:KEY3:require:SECRETS_FILE)%'

	<VirtualHost *:80>

	ServerName forum.example.com
	Redirect permanent / https://forum.example.com

	</VirtualHost>

	<VirtualHost *:443>

	ServerName forum.example.com

	Renew Puppet CA cert.

	Not the perfect idea, but should alleviate the need to resign every cert.

	What you need from existing puppet ssl directory:
	ca/ca_crt.pem
	ca/ca_key.pem

	Create an openssl.cnf:
	[ca]