extern/hishtory
1
0
Fork 0
mirror of https://github.com/ddworken/hishtory.git synced 2024-11-25 17:53:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

Rephrase README.md docs on self-hosting

Browse Source
This commit is contained in:
David Dworken 2023-09-12 08:21:43 -07:00
parent 514cf39c35
commit ea10050872
No known key found for this signature in database
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -132,7 +132,7 @@ By default, hiSHtory relies on a backend for syncing. All data is end-to-end enc
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`.
To make `hishtory` use your self-hosted server, set the `HISHTORY_SERVER` environment variable to the origin of your self-hosted server. For example, put `export HISHTORY_SERVER=http://my-hishtory-server.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.