xapian-omega package recommends apache2 | httpd-cgi,
and we don't want to run a web server on every system that builds our website.

Have the canonical tails.git trigger an ikiwiki update (on Git push) on www.lizard as well (refs: #14588)

… using the pingee plugin, again.

Trigger website updates via the ikiwiki pingee plugin instead of by pushing to a remote (refs: #14588)

This way, we get rid of the intermediate Git repo at webmasters.b.o
and directly ask the live website to pull from the canonical tails.git
(hosted on lizard) and then refresh itself.

Prepare code so that tails.git updates trigger a refresh of our website on www.lizard (refs: #14588).

This uses the https://ikiwiki.info/plugins/pingee/ plugin.

I'll enable this command once that instance of our website has CGI enabled.

So the build output does not depend on the umask of the user who might have
su'ed into the tails-website user and run ikiwiki by hand.

Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 502 on SERVER: <h2>Incomplete response received from application</h2>
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

This prevents tails::website from inheriting from tails::website::params.

We have to manage _hosting_ our website too so it's worth having a namespace.

These 4 repos are needed to build our website and were thus hosted at boum.org
so far.