Repository navigation
MyGraph 0.2.0
MyGraph can now serve HTTPS itself, so a server on your network no longer needs a reverse proxy to keep keys and data encrypted.
HTTPS
- Give the server a certificate and key, and it speaks HTTPS on its usual address:
[tls] certandkeyinserver.toml, orMYGRAPH_TLS_CERTandMYGRAPH_TLS_KEY. - A renewed certificate (from certbot, acme.sh or a NAS) is picked up within a minute, without a restart.
- The
mygraph mcpbridge acceptshttps://URLs. For a self-signed certificate or a private CA, pass--ca-cert <file.pem>or setMYGRAPH_CA_CERT. - A client that still uses
http://gets a clear error (api.https_required) telling it to switch, instead of garbled output. - With Docker,
compose.yamlmounts a certificate folder (MYGRAPH_CERTS); see.env.example. - Without a certificate, a server listening beyond its own machine logs a warning that traffic is unencrypted.
The README's new HTTPS section shows how to set this up, including a one-line command for a self-signed certificate.
Upgrading from 0.1.0
Nothing changes unless you set a certificate: the server keeps speaking plain HTTP, and storage is unchanged. If you turn HTTPS on, switch every client to https://, and update the mygraph bridge program on client machines to this version, because the 0.1.0 bridge can't connect to an HTTPS server.
Downloads
Download the archive for your platform and the embedding model, and unpack the model next to the mygraph binary. The Quick start explains each step. Docker: ghcr.io/dieron/mygraph:0.2.0.
Full changelog: v0.1.0...v0.2.0