fullsizemalt ca8a3e8cee

Test / backend-test (push) Waiting to run

Details

Test / frontend-test (push) Waiting to run

Details

refactor: Rebrand from 777wolfpack/CA Grow Ops to Veridian

- Update all frontend branding (Login, Splash, Layout, Navbar, etc.)
- Update page titles and breadcrumbs
- Update visitor components (Badge, CheckIn)
- Update deploy.sh and README
- Update test fixtures with new email domain

2025-12-27 11:24:26 -08:00

1.5 KiB

Raw Blame History

description
Deploy ca-grow-ops-manager to multiple environments

Deploying CA Grow Ops Manager

Prerequisites

SSH access to target servers (veridian, tangible-aacorn, etc.)
Forgejo accessible at https://git.runfoo.run

Deployment Environments

Test: veridian.runfoo.run (Staff Testing)
Prod: tangible-aacorn (Client Production)
Legacy: nexus-vector

Manual Deployment

// turbo-all

1. Run Deployment Script

From your local machine:

# Deploy to Test (Veridian) - Default
./deploy.sh test

# Deploy to Production (Tangible-Aacorn)
./deploy.sh prod

2. What happens?

The script will:

Push local code to Forgejo.
SSH into the target server.
Sync the repository.
Build and restart containers using Docker Compose.
Perform a health check.

CI/CD (Automatic)

Pushing to main triggers the default pipeline defined in .forgejo/workflows. Currently, this may target the legacy nexus-vector or reference the new servers depending on your deploy.yml configuration.

Troubleshooting

Deployment Fails

Permission Denied: Check your SSH keys and access rights to the server.
Environment Issues: Check .env files on the server (/srv/containers/...).

Logs:

ssh admin@veridian.runfoo.run "cd /srv/containers/ca-grow-ops-manager-test && docker compose logs -f"

URLs

Test Site: http://veridian.runfoo.run:8010 (Example)
Repo: https://git.runfoo.run/malty/ca-grow-ops-manager

1.5 KiB Raw Blame History