d0c43425f54a50cf43333d3264e27287f25b6363
Unit Tests / test (push) Successful in 12s
## Summary - Closes #33 - Create the draft invoice first, then attach the line item to that invoice id before finalize. Stripe's current API defaults `pending_invoice_items_behavior` to `exclude`, so the old pending-item-then-create-invoice order produced an empty invoice. Finalizing a $0 invoice auto-marks it paid. - If the finalized total does not match `amount_cents`, void the Stripe invoice and do not store `paid`. Ignore `invoice.paid` webhooks whose Stripe total is $0 when the local amount is non-zero. ## Test plan - [ ] Create a one-off invoice for $2040.00 for a test customer - [ ] Confirm the local invoice status is Open and the amount is $2040.00 - [ ] Open the Stripe hosted invoice and confirm the total is $2040.00 and status is Open, not Paid - [ ] Confirm a real `invoice.paid` webhook still marks a non-zero invoice paid after the customer pays Reviewed-on: #34
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>.
Languages
CSS
42.2%
JavaScript
24.1%
Python
16.8%
HTML
16.5%
Shell
0.3%