I went through the entire `nagios-master.cfg` file *again* and made
sure we had everything. I found a few things missing, but nothing
critical. Phases A and B were modified accordingly, in
team#41633 and team#41639.

Closes: team#41713

This was built on the fly to describe to @lelutin how that stuff work,
on a pad with a electronic pen, live, and could use some love.

Since the previous commit pointed out that there were dangling links to
the old staging URLs, I found out there are other dangling links that
also need to be replaced.

intrigeri authored 7 months ago and lelutin committed 7 months ago

The old URI gives me 404, while the new one announced in
https://forum.torproject.org/t/tor-project-updates-from-the-web-front/2788
does work.

port 8080 is fairly popular so many things can be binding to that port.
Today I had a container running that was bound to it and puppetdb
queries would not work (quite unsurprisingly). The cumin function in the
trick for automatically setting up the tunnel now checks whether the
port will respond to a simple puppetdb query.

`echo -e` was a typo. really I wanted that to be `-n` so that the dots
showing the waiting would be on the same line. The new `echo "x"` is
there to indicate the error in the waiting line but also to move the
error message to a new line, where it's easier to read

...in case folks don't have that in their ssh config already

I was tired of having to remember how to manually set this up after
having been yelled at by cumin.

IRC matrix bridge: add step-by-step instructions for internal channels

See merge request !51

This is probably important enough to be "top level"

The information was all already there, but I think having it as a
step-by-step list of instructions will be easier to understand,
especially for someone not already familiar with IRC.

Tbsync's caldav/carddav backend is no longer compatible with recent
versions of Thunderbird and so this method doesn't work anymore.

This was super not obvious when I needed to test connecting there at
first. Let's hope this'll make it more obvious to others in the future.

reading json logs is not natural and jq can be complicated to use
sometimes.

Because of discussions today around issue team#41675 and from
what I read in this wiki page, I somehow thought that only the .mbox
archive would be kept around and that the web archive would become
offline upon deletion.

But what happens is rather more to-the-letter what is said in this page:
the archive is kept around, html files visible on the web included.

I'm just clearing out the possible questions that I'll have (and
possibly others?) when I won't remember this detail by adding a quick
note about the web archive remaining online.

The main tor website is not manage by the www rotation (anymore?) it's
now getting auto-deployed by CI, except for prod.

The current text is confusing in that regards.

I had to do this again today for team#41667 and it was really
useful to have this around. I also noticed I was missing the `amtool`
invocation, even from the other ticket, so it was kind of important to
add this to the wiki immediately after all.

Alertmanager is now publishing alerts to the newly-registerd #tor-alerts
channel.

We've decided to change the channel name since the new monitoring system
is not related to nagios anymore. We prefer having a more generic name.

See team#41631

The linter I use locally (markdownlint) is set to be very strict and
there are many other issues that I didn't fix. The other issues are
almost all about lines being too short or bullet lists being indented by
one space. I just wanted to fix the easiest details that surely won't
have an impact on the content.

the output of `trocla --help` is really not helpful. With the README
file at least we can see what other subcommands exist and how they're
used.

There was a URL defined for "Trocla" but it wasn't used, so I just
linked it up on the first appearance of the software name.

service/ci: expand on workaround for team#41621

See merge request !50