I hadn't understood: The PaymentServer turns 16 vouchers into
50 k ZKAPs.  So far, we don't have a metric for used up ZKAPs.

Also, since the dashboard is already a full browser page and
only handling payment, I rename the services dashboard to payment
dashboard.

Fixes privatestorageops#349.

... so it can be used in the nginx config instead of duplicating the number

As per @jcalderone and @florian videoconf on 2021-08-06.

- Remove custom handling of Let's Encrypt certs, use NixOs' ACME
  integration instead.

- Use NGINX for TLS termination.

Tryfix. Can't run this locally ATM.

System tests do currently not include testing our monitoringvpn wireguard
setup, so let's just add the required IP by an alias to the lo interface.

This should fail currently, since metrics are still public.
Also, I couldn't test this code locally, since I currently run VirtualBox VMs
on my dev box. I'll just see what CI says to this code.

We have to explicitely add the port number so the relabel
config can strip it out again.  Else, `instance' seems to
get its value from somewhere else - somewhere our relabel
config does not look at.

Jean-Paul Calderone authored 3 years ago and Florian Sesser committed 3 years ago

This causes NixOS to generate the systemd timer unit for us and saves us
having to explain a lot of subtle systemd features.

It does pin execution to midnight on Monday but scaling to handle load spikes
is Let's Encrypt's problem, I guess.

This causes NixOS to generate the systemd timer unit for us and saves us
having to explain a lot of subtle systemd features.

It does pin execution to midnight on Monday but scaling to handle load spikes
is Let's Encrypt's problem, I guess.

We can't point it at a Nix expression that evaluates to our desired version of
nixpkgs because certain consumers want it to be a filesystem path instead.

This is what we wanted and much more directly.  It also avoids the gradual
lengthening of the path by always setting the path to nixpkgs-2105 instead of
some derivative of whatever the path was last time.

This commit does not change the semantics, only the looks.

At least it's easy to turn on

This is used in constructing the Google OAuth2 login callback URL and has to
match what's configured in Google - also helps if it is actually the address
of the server.

The old version of nixpkgs let us get away with setting neither isNormalUser
nor isSystemUser but setting all of the things a normal user would get
directly.  The new version of nixpkgs demands one of these flags be set.  So,
set it, and remove all of the redundant settings that it implies.

I hope I'm almost done with this branch.