mirror of
https://github.com/ddworken/hishtory.git
synced 2024-11-22 16:24:00 +01:00
Add instruction to direct client to self-hosted server
This commit is contained in:
parent
9b871e93ed
commit
7c8359ceb3
@ -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.
|
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.
|
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.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user