westfarnandCursor
5d378b7b19
The production .env stores DJANGO_ALLOWED_HOSTS as a JSON array (legacy format), but env_list only split on commas, yielding broken entries like '["aimloperations.com"' and causing DisallowedHost (HTTP 400) for every request. Parse JSON arrays as well as comma-separated values. Co-authored-by: Cursor <cursoragent@cursor.com>
company_site
Django site for AIML Operations.
Local development (uv)
uv sync
cp .env.example .env
cd company_site
DJANGO_ENV=dev uv run python manage.py migrate
DJANGO_ENV=dev uv run python manage.py runserver
Docker (dev + Postgres)
cp .env.example .env
docker compose up --build
Environments
Set DJANGO_ENV to one of:
| Value | DEBUG default | Logging level |
|---|---|---|
dev |
true | DEBUG |
beta |
false | INFO |
prod |
false | WARNING |
Secrets and service config come from environment variables. See .env.example.
CI / deploy workflows
| Workflow | Trigger | What runs |
|---|---|---|
.gitea/workflows/ci.yml |
Pull requests to master |
Unit tests only |
.gitea/workflows/deploy.yml |
Push to master |
Unit tests → Docker build/test → deploy |
Deploy never runs on pull requests. Uses separate workflow files (not job if conditions) so Gitea runners handle it reliably.
Production deploy
Server keeps its own .env at the live site path. Deploy rsyncs code but never overwrites .env.
- On the server, copy
.env.prod.exampleto.envand fill in production values. - Run
bash scripts/validate-env.sh /path/to/.envto verify required variables. - Push to
master— the deploy workflow runsscripts/deploy.sh, which:- rsyncs checkout to live site (preserving
.env) - validates environment variables
docker compose -f docker-compose.prod.yml builddocker compose up -d- runs migrations in the web container
- rsyncs checkout to live site (preserving
Legacy venv/systemd deploy: DEPLOY_MODE=legacy bash scripts/deploy.sh <checkout>.