westfarn af81d64267
Unit Tests / test (push) Successful in 11s
Add retail catalog add-ons to /web_design pricing table (#32)
## Summary
- Closes #31
- Add e-commerce, POS sync, event ticketing, and shipping rows to the `/web_design` estimator
- Auto-select deps match the Django template: shop needs email/SMS + Stripe; POS/shipping need shop; tickets need email/SMS + Stripe
- Update WebMCP `estimate_web_design_cost` ids and page copy

## Test plan
- [ ] `/web_design` shows the four new rows with build/monthly prices
- [ ] Toggling E-commerce checks Email & SMS + Payments
- [ ] Toggling POS or Shipping also checks E-commerce (and its deps)
- [ ] Toggling Event ticketing checks Email & SMS + Payments
- [ ] Unchecking Email & SMS unchecks payments, shop, POS, events, shipping as required
- [ ] Estimate totals and contact CTA feature list include the new ids
- [ ] `WebDesignPricingTests` + WebMCP estimate tool still pass

Reviewed-on: #32
2026-09-06 04:26:03 -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%