Repository files, collaboration, releases and project activity.
ARCHFORGE HISTORY
Blame · BRANDING-FIX-V109.md
Branch main · the Commit author is not necessarily a verified ArchForge account.
2109dd33b8archadmin2026-10-12
1 # Fix reverting Git labels — Debian 13 / ArchForge Git2109dd33b8archadmin2026-10-12
2 2109dd33b8archadmin2026-10-12
3 **Symptom:** `Git SSH` and `Git Smart HTTP` come back on the status site, even though you previously renamed both rows in the SQLite database.2109dd33b8archadmin2026-10-12
4 2109dd33b8archadmin2026-10-12
5 **What was fixed:** Earlier versions could overwrite the database display names from the service definitions. Version 1.0.9 enforces the public names in SQLite and in the web rendering code and verifies that you really deployed the current version.2109dd33b8archadmin2026-10-12
6 2109dd33b8archadmin2026-10-12
7 ## Upgrade from 1.0.82109dd33b8archadmin2026-10-12
8 2109dd33b8archadmin2026-10-12
9 1. Apply the small **1.0.9 update ZIP** over your 1.0.8 Git source repository, or use the full 1.0.9 source. Commit and push to your ArchForge repository.2109dd33b8archadmin2026-10-12
10 2. Connect to **VPS 2** with PuTTY. In your existing root shell, run:2109dd33b8archadmin2026-10-12
11 2109dd33b8archadmin2026-10-12
12 ```bash2109dd33b8archadmin2026-10-12
13 cd ~/archforge-external-status2109dd33b8archadmin2026-10-12
14 git pull --ff-only2109dd33b8archadmin2026-10-12
15 bash ./fix-status-branding.sh2109dd33b8archadmin2026-10-12
16 ```2109dd33b8archadmin2026-10-12
17 2109dd33b8archadmin2026-10-12
18 3. After it reports `Done`, press Ctrl+F5 at `https://status.archforge.nl`.2109dd33b8archadmin2026-10-12
19 2109dd33b8archadmin2026-10-12
20 The script first checks its checkout version (must be `1.0.9`), deploys with the normal database backup, checks that the installed files actually match the Git checkout, verifies the **running** service via `/healthz`, and displays the two saved labels from SQLite.2109dd33b8archadmin2026-10-12
21 2109dd33b8archadmin2026-10-12
22 Expected saved names:2109dd33b8archadmin2026-10-12
23 2109dd33b8archadmin2026-10-12
24 ```text2109dd33b8archadmin2026-10-12
25 git_http|ArchForge HTTPS2109dd33b8archadmin2026-10-12
26 git_ssh|ArchForge SSH2109dd33b8archadmin2026-10-12
27 ```2109dd33b8archadmin2026-10-12
28 2109dd33b8archadmin2026-10-12
29 If you are **not root**, use `sudo bash ./fix-status-branding.sh` in the last command instead.2109dd33b8archadmin2026-10-12
30 2109dd33b8archadmin2026-10-12
31 ### What remains unchanged2109dd33b8archadmin2026-10-12
32 2109dd33b8archadmin2026-10-12
33 - `/var/lib/archforge-status/status.db` and its samples/history2109dd33b8archadmin2026-10-12
34 - `/etc/archforge-status/status.env` and your Discord/SMTP settings2109dd33b8archadmin2026-10-12
35 - Caddy, TLS, DNS and the external domain2109dd33b8archadmin2026-10-12
36 - Your admin account and 2FA2109dd33b8archadmin2026-10-12
37 - The actual Git transport and internal SQLite service IDs2109dd33b8archadmin2026-10-12
38 2109dd33b8archadmin2026-10-12
39 **Note:** Running code from a release should be reviewed first, especially before running the deployment script as root. Version 1.0.9 is not yet tested on your own VPS.