extern/hishtory
1
0
Fork 0
mirror of https://github.com/ddworken/hishtory.git synced 2024-11-22 08:14:02 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add instruction to direct client to self-hosted server

Browse Source
This commit is contained in:
Nguyễn Hoàng Đức 2023-09-12 19:26:06 +07:00 committed by GitHub
parent 9b871e93ed
commit 7c8359ceb3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -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.