QNimbus

avg_time() {
  #
  # usage: avg_time n command ...
  #
  n=$1; shift
  (($# > 0)) || return                   # bail if no command given
  for ((i = 0; i < n; i++)); do
      { time -p "$@" &>/dev/null; } 2>&1 # ignore the output of the command
                                          # but collect time's output in stdout
  done | awk '

QNimbus

#!/usr/bin/env bash
##
## Title:                     deploy_homeassistant.sh
## Description:               Script to deploy uploaded certificates for use with Home Assistant
## Author:                    B. van wetten
## Created date:              28-12-2020
## Updated date:              28-12-2020
## Version:                   0.1
## GitHub Gist:               https://gist.github.com/cb7a61d4be538f80ccac7186a84e5ed4
##

QNimbus

blueprint:
  name: Motion-activated Light
  description: Turn on a light when motion is detected...
  domain: automation
  source_url: https://gist.github.com/d7384358e6078e9d3add226d1c54ed87
  input:
    motion_entity:
      name: Motion Sensor
      selector:
        entity:

QNimbus

{
  "271-4096-258": [
    {
      "type": "light",
      "object_id": "dimmer",
      "values": [
        "38-1-0"
      ],
      "discovery_payload": {
        "schema": "template",

QNimbus

# In addition to the material design icons - Home Assistant has some builtin icons as well

hass:account
hass:alert
hass:alert-circle
hass:altimeter
hass:apple-safari
hass:apps
hass:arrow-bottom-left
hass:arrow-down

QNimbus

---
- hosts: all:!localhost
  gather_facts: no

  # This play attempts to establish an SSH connection with inventory hosts
  # and when it encounters an expired password it will change and reset the password
  # so other playbooks and roles can normally execute without failing because of expired password.

  # Tested with:
  # - Ubuntu

QNimbus

#!/usr/bin/env bash
##
## Title:                     create_docker_certs.sh
## Description:               Short script to generate Docker server and client certificates to enable TLS communication
## Author:                    B. van wetten
## Created date:              25-05-2020
## Updated date:              25-05-2020
## Version:                   0.0.1
## GitHub Gist:               https://gist.github.com/QNimbus/19a53ce305e43b12434ddcac740e7bfe
##

QNimbus

{
    "$help": "https://aka.ms/terminal-documentation",
    "$schema": "https://aka.ms/terminal-profiles-schema",
    "actions": 
    [
        {
            "command": 
            {
                "action": "copy",
                "singleLine": false

QNimbus

#!/usr/bin/env bash
##
## Title:                     deploy_adguard.sh
## Description:               Script to deploy uploaded certificates for use with AdGuard Home DNS Server
## Author:                    B. van wetten
## Created date:              13-05-2020
## Updated date:              13-05-2020
## Version:                   0.1
## GitHub Gist:               
##

QNimbus

Source: electron/electron#9920 (comment)

I hope that this comment get noticed, because a lot of people are asking about importing fs or ipcRenderer in your apps. It's a common-need for electron apps but I found not many people have got it right, and are using outdated patterns. tl;dr - there is a security vulnerability if you don't import your node module (ie. fs) or electron module (ie. ipcRenderer) in the correct way. If you are using your app for only yourself you are probably safe, but if you ever want to share or sell your app you should read ahead.

Our goal

Before I go into the solution, it's important to understand why we are doing this in the first place. Electron apps allow us to include node modules in our apps, which gives them amazing power, but security concerns. We want to allow our app to use native-os (ie. node) features, but we don't want them to be abused.

> As brough