WIP: Fix discrepancy between NEO/go and NEO/py: Expand ~ in TLS key/certificate file paths
Good day Kirill,
as we discussed in nexedi/slapos!1307 (closed) I started to work on a patch for NEO/go which lets NEO/go expand the
~ prefix for the TLS key/certificate file paths.
I implemented the functionality in the new
xpath package (maybe it's rather an extension of
os/user than of
I locally run
go test in
neo/go/neo path and tests passed so far.
While I added unit tests for the new
ExpandTilde function, I didn't add specific tests inside
My initial idea is to add one more option to
NEOPySrv which declares whether the base path for the certificates/keys is with
~ or without
Then we switch between this new option here.
Does this sound reasonable to you?