Files

T

Gmer4Lfe 223d5ebfc9 Fix GITEA_DOMAIN value — was set with an https:// scheme prefix

git_pull_execute.sh, varaverk.plg, and gitea_ssh_setup.sh all treat
GITEA_DOMAIN as a bare hostname (gitea_ssh_setup.sh even builds its own
https:// API URL from it). The live value on HOST1 had the scheme
included, which would build a malformed SSH URL
(ssh://git@https://git.gmer4lfe.com:221/...) — hadn't been hit yet since
HOST2's install succeeded via Tailscale peer detection before ever
reaching this fallback tier.

2026-07-04 23:10:05 -04:00

master.conf

Fix GITEA_DOMAIN value — was set with an https:// scheme prefix

2026-07-04 23:10:05 -04:00

README.md

move conf templates and conf_populate to Deployment/; add rogue-prevention rules to CLAUDE.md

2026-06-14 13:18:08 -04:00

README.md

Configurations/

Runtime home for the live conf files. These are gitignored — never committed.

File	Source
`master.conf`	Seeded from `Deployment/master.conf.template` on first install
`host1.conf`	Seeded from `Deployment/host.conf.template` on first install
`host2.conf`	Seeded from `Deployment/host.conf.template` on first install

Templates and tooling live in Deployment/:

Deployment/host.conf.template — canonical template for new host confs
Deployment/master.conf.template — canonical template for master.conf
Deployment/conf_upgrade.sh — merges schema changes into existing confs
Deployment/conf_populate.sh — auto-detects and fills arr keys on first run