From 7c8359ceb3fa7631ee1b994221cf19f731db4867 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nguy=E1=BB=85n=20Ho=C3=A0ng=20=C4=90=E1=BB=A9c?= Date: Tue, 12 Sep 2023 19:26:06 +0700 Subject: [PATCH] Add instruction to direct client to self-hosted server --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4ea79f5..925b332 100644 --- a/README.md +++ b/README.md @@ -130,7 +130,9 @@ Download the latest binary from [Github Releases](https://github.com/ddworken/hi By default, hiSHtory relies on a backend for syncing. All data is end-to-end encrypted, so the backend can't view your history. -But if you'd like to self-host the hishtory backend, you can! The backend is a simple go binary in `backend/server/server.go` (with [prebuilt binaries here](https://github.com/ddworken/hishtory/tags)). It can either use SQLite or Postgres for persistence. +But if you'd like to self-host the hishtory backend, you can! The backend is a simple go binary in `backend/server/server.go` (with [prebuilt binaries here](https://github.com/ddworken/hishtory/tags)). It can either use SQLite or Postgres for persistence. + +To make `hishtory` use your self-hosted server, set environment variable `HISHTORY_SERVER` to your domain. For example if you use Bash, put `export HISHTORY_SERVER=https://api.example.com` at the end of your `.bashrc`. Check out the [`docker-compose.yml`](https://github.com/ddworken/hishtory/blob/master/backend/server/docker-compose.yml) file for an example config to start a hiSHtory server using postgres.