Waters ChurchandClaude Opus 5
67bcd3640a
ProdDash fetched one tar.gz of the branch from GitHub's codeload host, with that URL shape hardcoded. A `forge` setting now names where the code comes from: absent or "github" behaves exactly as before, and a Gitea or Forgejo base URL such as http://10.3.8.90:3000 fetches from a server of your own. Gitea spells an archive URL differently — /archive/<branch>.tar.gz rather than /tar.gz/<branch> — and that is the only real difference. Its tarball carries the same pax header with the same commit hash, so the archive parser, update detection and module installs are untouched. The "what changed" link follows the forge too, using each one's own compare and commits paths. Verified against both: the same commit and version come back from GitHub and from a self-hosted Gitea, and a module installs from each. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
8 lines
124 B
JSON
8 lines
124 B
JSON
{
|
|
"port": 24500,
|
|
"adminPasscode": "",
|
|
"forge": "github",
|
|
"repo": "michaelmcgary2008/ProdDash",
|
|
"branch": "main"
|
|
}
|