This is the derivation I use when running `nix store diff-closures` for the
weekly nixpkgs update.

The derivation also includes some attributes that are useful for exploring the
various grid configurations in the nix repl.

Note that changing the origin repository in the on-node deployment checkout
is also required.

See https://whetstone.private.storage/privatestorage/privatestorageops/-/merge_requests/197#note_19071

So perhaps it is impossible for anyone to approach the payment server from
these other domains now.

Mostly though I want to force CI to run because whetstone is not currently
showing the pipeline status for this MR...

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

... just because I like to be consistent.

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

... to make private.storage the default above privatestorage.io.
Before this the privatestorage.io could be seen in the TLS cert.

Source: https://whetstone.privatestorage.io/privatestorage/PrivateStorageio/-/merge_requests/237#note_18712

The current code evaluates our custom packages once for each node, which adds
signifcant amount of time to evaluate a grid. We can reduce this, by adding the
custom package set as an attribute to the nixpkgs set we pass to morph.

This doesn't change how we refer to those packages, as we continue to expose the
custom package set as a module attribute.

These are the times to evaluate all three grids (on a partially loaded system),
when there was nothing new to build:

```
before:
real	2m27.837s
user	3m35.528s
sys	0m3.722s

after:
real	1m12.748s
user	1m34.047s
sys	0m3.346s
```

For some reason this had eluded my earlier grepping.

Grafana 8 on NixOS 21.11 fails harder than 7.x on 21.05 when its
`grafana-admin.password` file is missing.  Provide it regardless
whether Google auth is configured or not.

The VirtualBox documentation says this is the network to use for host-only
networking.

mkfs silently truncates "zkapissuer-database" to "zkapissuer-datab" and
everything falls apart.

The point is this is where PaymentServer's persistent state goes.  That
includes vouchers but might include more stuff too.

The hardware modules can now configure this fileSystem in a way appropriate
for themselves and the issuer module can enable that configuration when it is
enabled itself.

now all nodes load the issuer module so we can always supply issuer
configuration, where it makes sense to do so, even on systems where the issuer
is not going to be enabled.

if that sounds silly read the comment in default.nix

Thanks @tomprince!

Copy everything from how the issuer does it.

As per our discussion in PrivateStorage sync meeting today.

The Blackbox exporter can be used to check whether some services do answer;
We'll use it for our HTTPS endpoints.
Especially handy is it's checking for TLS cert expiry.