In #641 I assumed that the .env file on the server would be loaded at startup by the Server.purs module. But that is not the case: it attempts to load the one present in the current working directory. We need to source the values from the /var/lib/registry-server directory instead. This PR accomplishes that, while still allowing local overrides via a .env file.
An alternate approach would be to adjust the 'loadEnv' function such that it tries to load the /var/lib/registry-server/.env file, then the local .env file, and do nothing in the module.nix service definition itself.
In #641 I assumed that the .env file on the server would be loaded at startup by the
Server.pursmodule. But that is not the case: it attempts to load the one present in the current working directory. We need to source the values from the /var/lib/registry-server directory instead. This PR accomplishes that, while still allowing local overrides via a .env file.An alternate approach would be to adjust the 'loadEnv' function such that it tries to load the /var/lib/registry-server/.env file, then the local .env file, and do nothing in the module.nix service definition itself.