jayjennings
c69eccb5c1
- Add incident reporting routes and logic to handle creation, updating, and retrieval of incidents. - Implement visibility rules for users based on roles (reporters, supervisors). - Create tests for incident reporting functionality to ensure correctness and reliability. - Introduce site and area management routes, including validation for area hierarchy. - Establish user management routes with role-based access control for creating and updating users. - Add setup routes for initializing the application with an organization and admin user. - Implement shared enums and schemas for consistent validation and data handling across the application. - Create a test helper for setting up an in-memory database and API client for testing. - Add TypeScript configuration for server-side code with strict type checking and module resolution.
16 lines
646 B
Bash
16 lines
646 B
Bash
# Copy to .env and adjust. All settings are optional for local development.
|
|
|
|
# Database. Defaults to embedded PostgreSQL (PGlite) stored in ./data/pglite.
|
|
# DATABASE_URL=postgres://safetylog:password@localhost:5432/safetylog
|
|
# DATABASE_URL=pglite://./data/pglite
|
|
|
|
# Port for the API server (and the web app in production).
|
|
# PORT=3000
|
|
|
|
# The URL people open in their browser. Use https:// in production so session cookies are marked Secure.
|
|
# PUBLIC_URL=http://localhost:3000
|
|
|
|
# Docker Compose only: password for the bundled PostgreSQL container.
|
|
# Use letters and numbers only (it is embedded in a connection URL).
|
|
# POSTGRES_PASSWORD=change-me
|