Repository files, collaboration, releases and project activity.
ARCHFORGE HISTORY
Blame · DEBIAN-13-GIT-URL-MIGRATION.md
Branch main · the Commit author is not necessarily a verified ArchForge account.
2109dd33b8archadmin2026-10-12
1 # Migrating your Debian 13 status VPS2109dd33b8archadmin2026-10-12
2 2109dd33b8archadmin2026-10-12
3 1. **Deploy ArchForge Website 11.3.7 first**. Verify `git ls-remote https://archforge.nl/archadmin/archforge-external-status.archforge HEAD` succeeds (PAT if repo is private).2109dd33b8archadmin2026-10-12
4 2. Publish the External Status **1.0.7 FULL/UPDATE** to your existing ArchForge repository (do not upload `.env`, SQLite, or secrets).2109dd33b8archadmin2026-10-12
5 3. With the repository checkout's original non-root owner, `cd ~/archforge-external-status && git pull --ff-only` while old transport is temporarily permitted on the website (if needed).2109dd33b8archadmin2026-10-12
6 4. Run `bash ./migrate-archforge-remote.sh` from that checkout. It first verifies the new URL with `git ls-remote`, then changes **only** `remote.origin.url`.2109dd33b8archadmin2026-10-12
7 5. If the ArchForge HTTPS monitor is configured, execute `sudo bash ./migrate-archforge-remote.sh --env-only` to update `/etc/archforge-status/status.env` with a timestamped backup; the service restarts. If you are logged in as root you may run the whole script once.2109dd33b8archadmin2026-10-12
8 6. Deploy the new app from your checkout as usual: `./update.sh` as the regular ArchForge owner (or `sudo bash scripts/deploy.sh "$PWD"` in a root-owned checkout, after reviewing code).2109dd33b8archadmin2026-10-12
9 7. Disable the temporary website `ARCHFORGE_LEGACY_GIT_URLS` flag. Future ArchForge pulls now use `.archforge`.2109dd33b8archadmin2026-10-12
10 2109dd33b8archadmin2026-10-12
11 Do not run `install.sh` again, delete `.git`, rename the bare repositories or move the SQLite DB.