env359 B
Environment File (.env template)
A sample environment (.env) file with typical configuration keys and placeholder values — for testing dotenv parsers and config loaders. Contains no real secrets.
Preview — first 11 linesenv
# Novus Examples — sample environment file (.env template).
# Copy to `.env` and fill in real values. Contains NO real secrets.
APP_NAME=novus-example
NODE_ENV=development
PORT=3000
DATABASE_URL=postgres://user:password@localhost:5432/example
REDIS_URL=redis://localhost:6379
API_BASE_URL=https://api.example.com/v1
FEATURE_FLAGS=beta,search
LOG_LEVEL=info
Specifications
- Format
- .env
- Keys
- 9
- Secrets
- none (placeholders only)
What is a .env file?
ENV files (dotenv) are plain-text lists of KEY=VALUE pairs used to define environment variables for an application, one per line with optional comments. They are conventionally excluded from version control because they often hold configuration and secrets. Parsing rules for quoting and interpolation vary by library.
How to use this file
Use an example env file to test dotenv parsers, key-value and quoting handling, and configuration loaders that inject variables into an application's environment.
Related files
- ymlDocker Compose File (YAML)A sample docker-compose file defining a web service with Postgres and Redis dependencies — for testing Compose parsers and YAML tooling.
- dockerfileDockerfile (multi-stage)A sample multi-stage Dockerfile with a build stage and a slim runtime stage — for testing Dockerfile parsers, linters (hadolint), and syntax highlighting. Illustrative only.
- webmanifestWeb App Manifest (webmanifest)A W3C Web App Manifest (JSON) with name, theme colours, and icon set — for testing PWA install prompts and manifest validators.
- jsonAPI Error — 404 (RFC 9457 problem+json)A 404 error body in RFC 9457 (problem+json) form, with type, title, status, detail, and instance — for testing structured error handling and problem-detail parsers.
- jsonAPI Error — 422 Validation (JSON)A 422 validation-error response with a machine-readable list of field errors — for testing form-validation surfacing and error mapping.
- jsonAPI Response — Users Page 1 (JSON)Page 1 of a paginated JSON API response (users), with page metadata and a `hasMore` flag. Paired with page 2 for testing pagination and infinite-scroll logic.
Generated by generation/data_dev_fixtures.py. Free for any use, no attribution required — license.