Move deployment workflow to Christ IT Gitea

docs/DEPLOYMENT.md

@@ -255,10 +255,16 @@ Initial test data/runtime:
 - No PHP-FPM version changes have been made.
 - No database server changes have been made.
 - Installed Composer on the remote server through Ubuntu packages so future updates can install PHP dependencies from `composer.lock`.
-- Converted `/sites/provider-exchange` from the initial rsync test deployment into a Git checkout of `https://github.com/jasonybird/technical-services-exchange.git`.
+- Converted `/sites/provider-exchange` from the initial rsync test deployment into a Git checkout.
 - Preserved the previous rsync deployment at `/sites/provider-exchange.pre-git-20260710-125739`.
 - Preserved the existing production `.env`, SQLite database, and Laravel `storage/` contents during the Git checkout conversion.
 - Confirmed remote Git checkout at commit `b45a9ec`.
 - Confirmed `bash scripts/update.sh` works from the remote Git checkout: Git pull, Composer install, npm install, Vite build, migrations, and Laravel cache rebuild completed successfully.
 - Confirmed remote working tree is clean after normalizing copied `storage/` placeholder file modes.
 - Confirmed authenticated smoke login with `admin@example.com` reaches `https://christit.com/tse/dashboard` and renders dashboard count content.
+
+2026-07-11:
+
+- Moved the canonical project remote from GitHub to Christ IT Gitea at `https://git.christit.com/technical-services-exchange/technical-services-exchange.git`.
+- Updated install/update documentation and installer defaults so future deployments pull from Christ IT Gitea.
+- Adopted the project convention that Git is the normal rollback trail; any future `.old` snapshots should be moved to an external archive safe outside the repo instead of retained in the workspace.

docs/FORWARD_PHASE_PLAN.md

@@ -25,7 +25,7 @@ The goal is not to clone Field Nation. The goal is to keep the useful operationa
 - Starter Sanctum API endpoints for providers, jobs, current user, work orders, and disputes.
 - Attachment policy with configurable disk, root, MIME allowlist, max size, previews, file metadata, and deletion.
 - Admin overview with counts and recent users/jobs/work orders/disputes.
-- Local-to-GitHub-to-ChristIT deployment workflow and docs.
+- Local-to-Christ-IT-Gitea-to-ChristIT deployment workflow and docs.
 
 ### Current Weak Spots In Code
 
@@ -707,7 +707,7 @@ Features:
   - thumbnail generation,
   - quotas,
   - private file access.
-- Add CI checks if GitHub Actions becomes useful.
+- Add CI checks if the Christ IT Gitea action runner becomes useful.
 
 Provider-protection rules:
 

docs/INSTALL.md

@@ -9,7 +9,7 @@ From a fresh Ubuntu host:
 ```bash
 sudo APP_URL=https://example.com \
     APP_DIR=/var/www/technical-services-exchange \
-    bash -c "$(curl -fsSL https://raw.githubusercontent.com/jasonybird/technical-services-exchange/main/scripts/install-ubuntu.sh)"
+    bash -c "$(curl -fsSL https://git.christit.com/technical-services-exchange/technical-services-exchange/raw/branch/main/scripts/install-ubuntu.sh)"
 ```
 
 The installer defaults to SQLite for a small test deployment. For production, use MariaDB/MySQL or PostgreSQL and set the database values in `.env` before running migrations.
@@ -37,7 +37,7 @@ APP_DIR=/var/www/technical-services-exchange bash /var/www/technical-services-ex
 The preferred working loop for this project is:
 
 1. Make and test changes locally.
-2. Commit and push to GitHub.
+2. Commit and push to the Christ IT Gitea repository.
 3. SSH to the server and run `bash scripts/update.sh` from the deployed Git checkout.
 4. Smoke test the live URL after the update completes.