10 Commits

Include renames

Author	SHA1	Message	Date
westfarn	8ccf17655d	updateing deploy for westfarn user	2026-07-08 12:26:07 -05:00
westfarn	04d842d799	Test who runs the job	2026-07-08 12:21:50 -05:00
westfarn	ae0f8a8bc5	Updated deploy to use act_runner keys	2026-07-08 11:51:33 -05:00
westfarn	16dfb3faae	Updated deploy to use act_runner keys	2026-07-08 11:46:43 -05:00
westfarn	9a383c0ee9	Update workflow to use server-infra	2026-07-08 06:05:11 -05:00
westfarn	426cc82f04	Dockerize Django app with dev/beta/prod env config and uv (#6) ... ## Summary - Containerize the Django app with Docker and docker-compose (dev + production) - Refactor settings into `dev` / `beta` / `prod` environments driven by environment variables - Connect to PostgreSQL via `DATABASE_URL` or `DB_*` vars - Migrate package management from pip to uv (`pyproject.toml`, `uv.lock`) - Split Gitea workflows: PRs run unit tests only; pushes to `master` run tests, Docker validation, and deploy - Update deploy script to rsync code, preserve server `.env`, validate config, and run Docker compose Closes #4 ## Test plan - [x] `uv run python manage.py test` passes locally (10/10) - [x] `DJANGO_ENV=beta` and `DJANGO_ENV=prod` load with correct logging levels - [x] `scripts/validate-env.sh` rejects missing production variables - [ ] `docker compose up --build` starts app + Postgres locally - [ ] Containerized unit tests pass in CI Docker job - [ ] Server `.env` created from `.env.prod.example` before first production deploy - [ ] CI workflow runs on this PR (tests only, no deploy) Reviewed-on: #6	2026-07-07 11:23:50 -07:00
westfarn	7dd5ec3be1	Add Employee vs Client user type and filter time/reports by employee (#14) (#15) ... ## Summary - Adds `UserProfile` model with mutually exclusive **Employee** / **Client** types - Replaces auto-Employee signal with auto-Client profile on user creation - Data migration: users with time log entries → Employee; others → Client (orphan Employee rows removed) - Admin UI at `/financial/manage_users` to set any user's type; profile page shows current type - **Employees** can log time; **Clients** get read-only access to reports and time logs - Time logs, reports, and dashboard filter to employees only - 14 new tests covering signals, type switching, access control, and filtering ## Design decisions (from issue Q&A) 1. Client login = read-only financial access (reports + time logs, no edit/log time) 2. Employee and Client are strictly mutually exclusive 3. Admins (superusers) can change type via Manage Users 4. Bulk migration applied for existing users ## Test plan - [x] `python manage.py test financial.tests` (14 tests pass) - [x] `python manage.py test public.tests` (21 tests pass) - [ ] Run migration on staging: `python manage.py migrate` - [ ] Verify admin can set user types at `/financial/manage_users` - [ ] Verify employee can log time at `/financial/timekeeping` - [ ] Verify client sees reports/time logs read-only, cannot log time - [ ] Verify employee filter dropdown excludes clients Closes #14 Reviewed-on: #15	2026-07-05 12:54:50 +00:00
westfarn	9c7e02e41e	Add unittests and fix tracking error	2026-06-28 06:55:44 -05:00
westfarn	7e448cf61a	Update .gitea/workflows/deploy.yml	2026-06-27 18:06:03 +00:00
westfarn	e625dc30ad	Updated to get gitea action runner	2026-06-27 12:19:54 -05:00