The church's own Gitea is where ProdDash lives
The shipped defaults pointed at GitHub, so a fresh install with no configuration would have looked there — and that repository is going away. They now name michael/ProdDash on chronicles-ab.waterschurch.org:3000, which a fresh install was verified to reach with nothing configured at all. The hostname rather than the IP, because the UniFi DNS record is authoritative and this survives the NAS changing address. Both production machines already carry an explicit setting of their own, so neither is affected either way. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
1c8cd63cd0
commit
1be5cbef31
@@ -766,7 +766,7 @@ function parseRepoSetting(value, fallbackBranch) {
|
||||
}
|
||||
|
||||
const REPO = parseRepoSetting(process.env.PRODDASH_REPO || shellConfig.repo, shellConfig.branch)
|
||||
|| parseRepoSetting('michaelmcgary2008/ProdDash', 'main');
|
||||
|| parseRepoSetting('michael/ProdDash', 'main');
|
||||
|
||||
/**
|
||||
* Which server the code comes from. GitHub unless `forge` names another —
|
||||
|
||||
Reference in New Issue
Block a user