Add an automatic build/install footer to the public Importarr UI, but do this after the server repo reinstall workflow works. The footer is needed so operators can see how old the live code is and whether a deploy actually reached the public site.
Requirements
Do not require manual updates.
Show at least:
git commit SHA
install/build timestamp in UTC
service start timestamp
package/app version if available
Prefer metadata generated by the install/upgrade script on server, for example /opt/importarr/build.env loaded by systemd.
The public page bottom/footer should make this visible without opening dev tools.
/api/status should expose the same build metadata for automated checks.
Acceptance criteria
After deploy/repo-upgrade.sh, the footer changes automatically to the deployed commit/timestamp.
https://importarr.example.com/ visibly includes the build/install metadata.
This is implemented only after the repo-managed server reinstall/update path is in place.
## Problem
Add an automatic build/install footer to the public Importarr UI, but do this after the server repo reinstall workflow works. The footer is needed so operators can see how old the live code is and whether a deploy actually reached the public site.
## Requirements
- Do not require manual updates.
- Show at least:
- git commit SHA
- install/build timestamp in UTC
- service start timestamp
- package/app version if available
- Prefer metadata generated by the install/upgrade script on server, for example `/opt/importarr/build.env` loaded by systemd.
- The public page bottom/footer should make this visible without opening dev tools.
- `/api/status` should expose the same build metadata for automated checks.
## Acceptance criteria
- After `deploy/repo-upgrade.sh`, the footer changes automatically to the deployed commit/timestamp.
- `https://importarr.example.com/` visibly includes the build/install metadata.
- `https://importarr.example.com/api/status` exposes structured build metadata.
- This is implemented only after the repo-managed server reinstall/update path is in place.
daniels
changed title from Add automatic build/install footer after dgsserver1 repo reinstall workflow to Add automatic build/install footer after server reinstall workflow2026-07-29 14:06:25 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Add an automatic build/install footer to the public Importarr UI, but do this after the server repo reinstall workflow works. The footer is needed so operators can see how old the live code is and whether a deploy actually reached the public site.
Requirements
/opt/importarr/build.envloaded by systemd./api/statusshould expose the same build metadata for automated checks.Acceptance criteria
deploy/repo-upgrade.sh, the footer changes automatically to the deployed commit/timestamp.https://importarr.example.com/visibly includes the build/install metadata.https://importarr.example.com/api/statusexposes structured build metadata.Add automatic build/install footer after dgsserver1 repo reinstall workflowto Add automatic build/install footer after server reinstall workflow