- Oct 13, 2021
-
- Oct 08, 2021
-
- Dec 10, 2020
-
-
Peter Palfrader authored
-
Peter Palfrader authored
-
- Nov 17, 2020
-
-
anarcat authored
-
- Oct 27, 2020
-
-
anarcat authored
-
- Oct 26, 2020
- Jun 25, 2020
-
- Jun 24, 2020
-
-
anarcat authored
-
anarcat authored
This is: ikiwiki2hugo.py --exclude .pytest_cache With the latest script from: <https://gitlab.com/anarcat/scripts/-/blob/master/ikiwiki2hugo.py> ... as of right now.
-
- Jun 15, 2020
-
-
anarcat authored
The latter is actually one of two standard file extensions (as per RFC7763, the other being .markdown). It's also the extension expected by GitHub, GitLab, and other wiki software. So for the sake of future-proofing and compatibility, rename all files to the new name. This will hopefully not break anything: the file extension is not present in the rendered version anyways.
-
anarcat authored
Those are more future proof and will work in gitlab.
-
- May 25, 2020
-
-
anarcat authored
Actually, "monitoring warnings" is less meaningful in some cases. For example in the case of tls, it talks about emails from Digicert, which is not per se a monitoring warning. Similarly, the Ganeti documentation talks about I/O overloads and other conditions that are not necessarily raised by the monitoring system, but could be raised by our "human nagioses" (e.g. "humans" saying "this is slow!"). This reverts commit 85d5423f.
-
anarcat authored
"Pager" and "playbook" have specific meanings which are not obvious to me. For example, we don't carry pagers and "playbooks" could be ansible playbooks, but we don't carry those either. I thought of naming this "Nagios warnings" but I figured I would be more forward-compatible (in case we switch away from Nagios) and name this "Monitoring".
-
- Mar 30, 2020
-
-
anarcat authored
-
- Mar 16, 2020
-