Paraphraser

Keybase proof

I hereby claim:

• I am paraphraser on github.
• I am paraphraser (https://keybase.io/paraphraser) on keybase.
• I have a public key ASAEuq9mHBtAWcvqsEvFAC-CtHGqjRDtQU3Ht7YY0MrSJQo

To claim this, I am signing this object:

Paraphraser

Configuring Raspbian to use local time-servers

The case for using local time-servers

Out of the box, Raspbian gets its time from NTP servers in the debian.pool.ntp.org domain. You can confirm this via:

$ timedatectl show-timesync
...
ServerName=0.debian.pool.ntp.org

Paraphraser

Tutorial: Enabling UDP support in InfluxDB

Assumptions:

• you are running SensorsIot/IOTstack with InfluxDB as one of the containers
• you want to enable UDP support
• your goal is to log traffic arriving on UDP port 8086 into an InfluxDB database named "udp".

This tutorial is specific to SensorsIot/IOTstack. You're on your own if you "get creative" and choose different ports or database names.

Paraphraser

UPS monitor - back end - proof of concept

Assumptions

• There exists a mechanism (unspecified) for acquiring status information from an Uninterruptible Power Supply;
• That mechanism is available to Node-RED; and
• There exists a Node-RED flow (unspecified) that is capable of interpreting the UPS status information and making decisions about when devices should power down and in what order.

Task Goal

Paraphraser

IOTstack: Understanding compose profiles

You are probably familiar with running a command like:

$ docker-compose up -d

You probably expect that command to bring up a container for every service definition mentioned in your docker-compose.yml. That's its default behaviour.

Paraphraser

IOTstack tutorial: InfluxDB data merging

Scenario

A question on Discord described a situation where a new (empty) database had been created. That database contained data acquired since the rebuild but had no historical data prior to the rebuild. However, the person did have a "portable" backup of the older data and wanted to know if it was possible to merge the backup with the live data?

The answer is "yes". Merging measurements will solve this particular problem.

My test environment

Paraphraser

IOTstack: InfluxDB 2 experiments

Update #1:

• Rewrite assuming user only has a single Raspberry Pi which is processing live data. Minimises the down time for InfluxDB 1.8.

---

This gist explains the steps I followed to:

Paraphraser

macOS Time Machine: restoring files owned by root

when you own the file …

On macOS, Time Machine pretty much just works. You delete or mutilate a file. Then you realise you want to get back to the older version so you:

1. Use the Finder to open the folder containing the file you want to restore.
2. Choose "Enter Time Machine" from the Time Machine menu.
3. Step back in the timeline until you find the version you want to restore.

Paraphraser

Hints: Running Node-RED in IOTstack

Much of the material that used to be in this gist has been moved to the Node-RED documentation page at SensorsIot/IOTstack.

The nodered_list_installed_nodes script is also part of the IOTstack repository.

---

The material below is the remainder of the original gist:

Paraphraser

Tutorial: Enabling authentication in InfluxDB

Assumptions:

• you are running SensorsIot/IOTstack with InfluxDB as one of the containers
• you want to enable authentication for your InfluxDB databases.

Note: This tutorial is specific to SensorsIot/IOTstack.

Definition: