Previous procedure wasn't really a full update, but with the "Update only
Docker images" procedure, full update can be made more complete. Even
though it's more burdensome to users, as it removes any docker-compose.yml
user made customization.

Adds InfluxDB 2 container and documentation.

Fixes #455, Fixes #289, Fixes #279, Fixes #169, Fixes #132

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

fixed minor typo in home assistant - about Supervised Home Assistant section.

20220602 InfluxDB 2 - master branch - PR 1 of 3

20220517 Grafana InfluxDB HealthCheck - master branch - PR 1 of 3

Doc improvements

Docs: Refactor to define anchors using attribute list

duckdns: add service

docs/Home: add full site page listing

Docs: fix and add missing code highlight

doc/home-assistant typo

Fixes #556

Fix to assume your RPi IP-address being 192.168.1.10 in all examples.
Previously some parts of the doc assumed 192.168.1.50.

Aim to improve beginner-friendliness:
* add admonition blocks for clearer subtopic parts
* change advanced parts into collapsed (expandable) admonitions blocksdocs/pi-hole: clarify order and collapse advanced sections

Aim to improve beginner-friendliness:
* clearer heading names
* change advanced parts into collapsed (expandable) admonitions blocks
* add some small explanations

Also fixes Wireguard id-attribute metadata syntax

Also:
* fix aliases to work regardless of user's current directory (using the
  '-f' flag instead of changing the directory would ignore a possibly
  existing `docker-compose.override.yml')
* fix iotstack_build alias to include "--pull --no-cache", as without
  these there may be cases where everything isn't fully updated.
* add the iotstack_update_docker_images alias to perform the basic
  container update.

Fixes #433

Also improves on exception reporting to include full stacktrace

Also add Changlog link to the Wiki homepage.

Use yaml structure from docker-compose-base.yml instead of creating it
in python.

Add compose variables and indentation as defined by #505

Fixes #383, Fixes #517

Implements and resolves #232

Also changes user to reflect the strong recommendation of #287

As %randomPassword% doesn't seem to work, change to use the default
password as listed on Default-Configs.md and add support for #505
style variables.

Change default public port from 5433 to avoid port-conflict with posgresql.

* manage python requirements using requirements-menu.txt
  installing the exact versions of all dependencies.
* is completely separate from any system-wide installed python packages,
  won't conflict with existing installed python packages.
* minimizes global system requirements down to python and python-virtualenv

virtualenv requires "--seed pip" or it fails with:
    ModuleNotFoundError: No module named 'pip._internal.utils'

Fixes some typos and updates some out-of-date information.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Works towards making the "Getting started" not so very long.

Resolves #58

Move "the nuclear option" from Getting Started.
Resolves #180 adding github gists link

Adopts build-argument syntax in the template service definition +
template Dockerfile to pass an image tag plus an optional list of
extra packages to the Dockerfile at build time.

Pinning to a specific base image can now be accomplished in the Compose
file. This places Node-RED on equal footing with containers that do not
use local Dockerfiles (and Mosquitto which already has similar
build-argument syntax).

Together, the changes mean user customisations to the first part of the
Dockerfile are no longer at risk of being overwritten by menu runs to
change the list of add-on nodes.

For any given IOTstack installation, there is some possibility of a
hybrid result, depending on how and when the user runs the menu, or
which techniques each user employs to manage their Compose file and
Node-RED Dockerfile. The intention is to either fail safe or at least
fail sensibly:

* old Compose + old Dockerfile = no change.
* old Compose + new Dockerfile will adopt `latest` so `node.js` *may*
change from 12.x to 14.x on the next `--build` but this will depend on
whether the user ever explicitly set `latest-14` in their old Dockerfile.
* new Compose + old Dockerfile = no change. The service definition build
arguments will be ignored and the user may be confused until consulting
the documentation, but the container will still build as before.
* new Compose + new Dockerfile will behave as per the revised
documentation. Absent any user changes to the service definition, the
resulting container will be based on `latest` (which implies `node.js`
14.x) and there will no packages other than `eudev-dev` (the existing
Dockerfile default).

Worst case is an existing user adopting all-new syntax without realising
the old Dockerfile specified `latest-12`, thereby advancing to `node.js`
14.x unexpectedly, perhaps also losing additional packages along the
way. The fix is to specify `DOCKERHUB_TAG=latest-12`, append any lost
packages to `EXTRA_PACKAGES=`, and rebuild.

Personally, I switched to `-14` a good six months ago. It worked
out-of-the-box with zero migration issues and I've never looked back.
While that's only n=1, I don't feel there's sufficient risk to warrant
IOTstack continuing to default to `-12`. We have to change sometime, or
we'll be back where we were when images based on `-10` were no longer
being offered as Node-RED marched forward.

Using `node.js` version 14 is the implicit recommendation (ie `latest`
and `latest-14` are currently synonyms). Version 16 is available but is
known to throw up some migration issues. IOTstack started defaulting to
version 12 in March 2021 (when version 10 was deprecated).

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Fixes `nodered_list_installed_nodes.sh`. Now relies on `npm` running
inside the container to discover what's installed where.

Documentation describing use of `/data` on `npm` calls turns out to be
ineffective. The solution is to set the working directory on the
`docker exec` call.

Following on from a discussion on Discord
[starting here](https://discord.com/channels/638610460567928832/638610461109256194/994818372439113838),
it was obviously confusing for the documentation to be discussing
"nodes" when `npm` can be used to install a variety of components.
Documentation adjusted to clarify this.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

The revised `nodered_list_installed_nodes.sh` revealed that the older
"move and delete" method for resolving conflicts actually leaves behind
a mess. Replaced with a `docker exec` call.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

A Discord thread starting at
https://discord.com/channels/638610460567928832/638610461109256194/1005812386688680006
revealed that the Domoticz would not function properly on a clean
install. The symptom was either a 400 or a 404 error, depending on the
URL.

Three issues identified with existing service definition:

1. Wrong image base. Should be "lscr.io/linuxserver/domoticz".
2. Wrong image tag. Should be "latest".
3. `network_mode: bridge`.

It has never been clear what `network_mode: bridge` is intended to do.
It is the only container with this option. While it may once have been
needed, its presence now appears to prevent the container from
responding correctly on port 8083.

No IOTstack documentation exists for this container. This PR adds some
basic documentation in the form of references to the Domoticz home plus
associated GitHub and DockerHub pages, along with an invitation for
someone who is familiar with the container to expand it further.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Adds first cut of ZeroTier in the form of two containers:

* ZeroTier-client from `zyclonite:zerotier`
* ZeroTier-router from `zyclonite:zerotier-router`

The two containers are mutually exclusive (no menu check - docker-compose
will complain about port conflicts). My guess is that IOTstack users will
generally prefer the router because it is closer to WireGuard
functionality, and is likely what an IOTstack user will be looking for
if they find themselves stuck behind CGNAT.

ZeroTier-client is the standard client. Has no environment variables or
other preconfiguration. Needs to be instructed to join the user's
ZeroTier network after first launch. Otherwise works "as is".

ZeroTier-router is built on top of ZeroTier-client and adds management
of iptables rules at startup/shutdown to support routing to/from the
local network. Has environment variables with defaults appropriate for
IOTstack.

Adds documentation:

* ZeroTier.md
* ZeroTier-vs-WireGuard.md to explain the pros/cons of each.

Modifies WireGuard documentation to reference ZeroTier-vs-WireGuard.md
and also adds a tweak to one diagram (takes the opportunity to switch
from PNG to JPEG ; PNGs do not always "play nice" when Wiki pages are
viewed in Dark Mode).

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

1. `npm list --depth=0 --parseable` was displaying an alert that the
user really can do nothing about:

	```
	npm ERR! extraneous: libmime@5.0.0 /usr/src/node-red/node_modules/node-red-node-email/node_modules/libmime
	```

	Suppress by redirecting stderr to null.

2. Construct command needed to remove blocking nodes and output it as
 a hint at the end of the run.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Expand InfluxDB 1.8 documentation by incorporating material from:

* [Tutorial: Enabling authentication in InfluxDB](https://gist.github.com/Paraphraser/9f3aa21fddd5d4e8141a7ab03ffb4dd7)
* [Tutorial: Enabling UDP support in InfluxDB](https://gist.github.com/Paraphraser/15483641fc657a147dfae7b03d291bc0)

I thought I had already added this material but a Discord question made
me realise I was mistaken.

General tidy-up because a lot of the example material was either wrong
or out-of-date.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

20220901 InfluxDB - master branch - documentation

20220811 ZeroTier - master branch - PR 1 of 2

20220810 domoticz - master branch - PR 1 of 3

20220708 Node-RED - master branch - PR 1 of 2

20220705 NextCloud documentation

webthingsio_gateway: fix template folder name

mkdocs: script automating python virtualenv use

menu: rename env.yml to docker-compose-base.yml

postgres: remove broken menu options and fix docs

Doc improvements

Timescaledb: fix broken template

menu: fix error on empty compose-override.yml

docs/Changelog: update to reflect latest changes

.bash_aliases: auto-remove orphan containers

docs/pi-hole: clarify and improve beginner-friendliness

Telegraf: report 'iotstack' as hostname to influx

Telegraf: fix deprecated options and doc typos

menu: run in python virtualenv

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

fix typo in CGNAT diagrams

Fixes the problem reported by #599.

This is an unfortunate, predictable and predicted side-effect of moving
from this style of anchored title:

```
```

to this style:

```
```

The former style is testable by generating HTML from the Markdown and
running it through a validator. The latter style isn't amenable to that
approach because anchor generation is done "just in time" by mkdocs.
Until we find some way to test mkdocs output in a systematic way,
fairly trivial semantic errors (like the missing "#" in this case) will
occasionally slip through the cracks.

Also fixed another broken link (`#authWarning`).

Fixes #599.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

20220913 Influx documentation - master branch

Fix typo in example - container should be referenced as `influxdb2`
across the internal bridged network.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Clarify what happens if the container starts with the default device
`/dev/ttyAMA0` in the service definition. The process probes the device,
finds it doesn't respond like a Zigbee adapter, and aborts without
starting the web GUI. Because of the `restart: unless-stopped` clause,
Docker restarts the container and the same sequence repeats.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

WireGuard has started renaming the `custom-services.d` and
`custom-cont-init.d` directories to have random suffixes, along with
the following README.txt:

```
********************************************************
********************************************************
*                                                      *
*                         !!!!                         *
* Custom scripts or services found in legacy locations *
*                         !!!!                         *
*    Please move your custom scripts and services      *
*    to /custom-cont-init.d and /custom-services.d     *
*    respectively to ensure they continue working.     *
*                                                      *
*  Visit https://linuxserver.io/custom for more info.  *
*                                                      *
********************************************************
********************************************************
```

Some existing installations have also failed. Remote clients are unable
to connect with `docker logs wireguard` cycling the following messages:

```
s6-supervise custom-svc-README.txt (child): fatal: unable to exec run: Exec format error
s6-supervise custom-svc-README.txt: warning: unable to spawn ./run - waiting 10 seconds
```

The container does not go into a restart loop so `docker ps` does not
alert the user to the situation.

This PR:

1. implements the required changes to the WireGuard service definition;
2. provides a script to assist with the necessary folder restructuring;
3. adds a section to the IOTstack WireGuard documentation (master
branch) to explain the process.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

A [Discord question](https://discord.com/channels/638610460567928832/638610461109256194/1028011748323762276)
revealed that the Portainer-CE UI no longer uses the term "endpoint".
It has been replaced with the term "environment". This PR updates the
documentation accordingly.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Adds `nodered_version_check.sh` script to scripts folder (previously
available via
[gist](https://gist.github.com/Paraphraser/c8939213faf2de8a10f2a1f67452b0c1#-useful-script-nodered_version_check-)).

Adds documentation to Node-RED wiki page.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

A Discord question has led to the discovert that the previous peer
name syntax which supported hyphens in names no longer works as
expected. Names now need to be like "identifiers", a letter followed
by letters and digits. Documentation updated accordingly.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Getting Started:

* Expands on PiBuilder option
* Explains purpose of dhcpcd patch

Troubleshooting:

* Adds section on device errors (eg ttyAMA0 not present on non-Pi
hardware)
* Adds section on system freezes. Primarily aimed at misbehaving SSDs.
Includes trying USB2 port, checking dhcpcd patch is in place, and adding
quirks string for some SSDs.

Touches-up some miscellaneous layout issues noted in passing.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

`raymondmm/tasmoadmin` on DockerHub was last updated two years ago.

Switches image to `ghcr.io/tasmoadmin/tasmoadmin:latest`.

Also adds `TZ` to template.

Removes `build.py` as not necessary.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Re-orders topology 1 reachability table so "from" host is on the left
with "to" host+interface on the right. I'm hoping this will lead to
improved understanding. Also adds dagger to one case omitted from
the original version.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Per issue #620, the default `config.yml` should reference:

	- `prometheus-cadvisor:8080` not `cadvisor:8080`
	- `prometheus-nodeexporter:9100` not `nodeexporter:9100`

Master branch doco updated to add migration tips.

Fixes #620

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Adds first-cut service definition for "scrypted" to master branch.

Only for testing at this point.

Minimal documentation added.

Not yet added to old-menu or experimental.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Fixes some incorrect discussion relating to old-menu/new-menu
differences.

Updates screen captures of Nextcloud GUI.

Adds explanation about networking. This follows on from a question
on Discord.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>

2022-12-01 Nextcloud documentation - master branch

2022-11-08 Prometheus defaults - master branch - PR 1 of 3

2022-10-11 ZeroTier - master branch

2022-10-28 basics documentation - master branch

2022-10-11 Node-RED version-check script - master branch - PR 1 of 3

2022-10-10 Portainer-CE documentation - environment

…estructure-master

2022-10-01 WireGuard volumes restructure - master branch - PR 1 of 3

2022-09-25 InfluxDB2 - master branch

2022-09-25 Zigbee2MQTT - master branch

2022-11-11 scrypted - master branch

2022-10-28 tasmoadmin - master branch - PR 1 of 3

Adds dependency checking for jq and rclone.

Signed-off-by: Phill Kelley <34226495+Paraphraser@users.noreply.github.com>