bunkhouse/vitals
9
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: point clone and documentation links at the real homes

Browse source 
The quickstart still told people to clone sastian/vitals on the forge,
which stopped existing when the repo moved to binaryranch-labs. A broken
clone command in the first code block is the worst place to have one.

Co-developed-with: CLU <clu@binaryranch.com>
This commit is contained in:
Christian Sass 2026-10-19 17:03:52 -05:00
parent cd6e76c830
commit f086afc030
2 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -68,11 +68,14 @@ serves a canned snapshot at the same URL, which is how the screenshot above was
made.
```bash
git clone https://forge.binaryranch.com/sastian/vitals.git
git clone https://github.com/BinaryRanch/vitals.git
cd vitals
python3 server.py # http://127.0.0.1:8791
```
Canonical development happens on [Binary Ranch's own forge](https://forge.binaryranch.com/binaryranch-labs/vitals);
GitHub is the public mirror. Either clone works, commits land in both.
Optional: run it as a user service so it is either up or reported, never a
silently orphaned process.

2
systemd/vitals.service
View file

@ -1,6 +1,6 @@
[Unit]
Description=Vitals — workload and browser-tab monitor
Documentation=https://forge.binaryranch.com/sastian/vitals
Documentation=https://github.com/BinaryRanch/vitals
After=graphical-session.target network.target
PartOf=graphical-session.target