Directing writes to the primary node is the job of the application, so the primary's hostname needs to be exposed somehow. At present the application can get this by querying Consul, but if #37 and/or #23 are implemented this will no longer be the case. I propose exposing this information via a file in the shadow directory, similar to Litestream's .primary.
I think I'll switch the .primary to show the hostname instead of the LiteFS URL endpoint. That really doesn't need to be exposed to the end user AFAICT.
Directing writes to the primary node is the job of the application, so the primary's hostname needs to be exposed somehow. At present the application can get this by querying Consul, but if #37 and/or #23 are implemented this will no longer be the case. I propose exposing this information via a file in the shadow directory, similar to Litestream's
.primary
.