westfarn 85369914c8
Unit Tests / test (push) Successful in 12s
Quote DEFAULT_FROM_EMAIL display name so contact mail sends (#29)
## Summary
- Closes #28
- Quote `DEFAULT_FROM_EMAIL` display name (`"AI ML Operations, LLC" <info@aimloperations.com>`) so RFC 5322 From parsing succeeds
- Update settings default, email send fallbacks, and `.env` examples

## Problem
Contact form saved leads but notification email to `ryan@aimloperations.com` failed with:
```
Invalid address; only AI ML Operations could be parsed from "AI ML Operations, LLC <info@aimloperations.com>"
```
Comma in unquoted display name treated as address-list separator.

## Test plan
- [ ] Submit contact form in an environment with SMTP configured
- [ ] Confirm lead appears on leads page
- [ ] Confirm email arrives at ryan@aimloperations.com
- [ ] If prod sets `DEFAULT_FROM_EMAIL` in `.env`, ensure that value is also quoted before deployReviewed-on: #29
2026-08-07 08:17:31 -07:00
2026-03-20 13:07:28 -05:00
2026-06-27 12:19:54 -05:00
2025-03-24 13:06:45 -05:00
2026-07-08 06:12:21 -05:00

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

App: http://localhost:8000

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.

  1. On the server, copy .env.prod.example to .env and fill in production values.
  2. Run bash scripts/validate-env.sh /path/to/.env to verify required variables.
  3. Push to master — the deploy workflow runs scripts/deploy.sh, which:
    • rsyncs checkout to live site (preserving .env)
    • validates environment variables
    • docker compose -f docker-compose.prod.yml build
    • docker compose up -d
    • runs migrations in the web container

Legacy venv/systemd deploy: DEPLOY_MODE=legacy bash scripts/deploy.sh <checkout>.

S
Description
Django site for company
Readme
47 MiB
Languages
CSS 42.5%
JavaScript 24.2%
HTML 16.6%
Python 16.3%
Shell 0.4%