# RapidKit Settings Module

Configurable application settings module with FastAPI and NestJS adapters.

This README follows the shared RapidKit module format:

1. **Overview & capabilities**
1. **Installation commands**
1. **Directory layout**
1. **Generation workflow**
1. **Runtime customisation hooks**
1. **Testing & release checklist**
1. **Reference links**

Use the same headings when documenting other modules so maintainers know what to expect.

As a RapidKit module, this module also follows the shared metadata/documentation standard:

- `module.yaml` is the canonical source of truth (including the `documentation:` map).
- Module docs live under `docs/` and should match the keys referenced from `module.yaml`.
- The module changelog is maintained in `docs/changelog.md` and referenced both from `module.yaml`
  and this README.

______________________________________________________________________

## Module Capabilities

- Centralised environment management built on Pydantic v2
- Optional dotenv loading, relaxed production guards, and structured refresh logging
- Health probes for FastAPI and NestJS generated services
- Vendor snapshots under `.rapidkit/vendor/settings/<version>` for reproducible installs
- Framework plug-in model, allowing additional adapters to register with the shared registry

______________________________________________________________________

## Install Commands

```bash
rapidkit add module settings
```

Re-run `rapidkit modules lock --overwrite` after adding or upgrading the module so downstream
projects capture the new snapshot.

### Quickstart

Follow the end-to-end walkthrough in `docs/usage.md`.

______________________________________________________________________

## Directory Layout

| Path               | Responsibility                                                              |
| ------------------ | --------------------------------------------------------------------------- |
| `module.yaml`      | Canonical metadata (version, compatibility, documentation map)              |
| `config/base.yaml` | Declarative spec that drives prompts and dependency resolution              |
| `generate.py`      | CLI/automation entry point for rendering vendor and project variants        |
| `frameworks/`      | Framework plugin implementations registered via `modules.shared.frameworks` |
| `overrides.py`     | Runtime opt-in hooks applied via environment variables                      |
| `docs/`            | Module docs referenced from `module.yaml` (usage/overview/changelog)        |
| `templates/`       | Base templates plus per-framework variants                                  |

______________________________________________________________________

## Generation Workflow

1. `generate.py` loads `module.yaml` and checks version drift with
   `modules.shared.versioning.ensure_version_consistency`.
1. Vendor artefacts are rendered from templates into `.rapidkit/vendor/...` for reproducible
   installs.
1. The requested framework plugin maps templates into project-relative paths.
1. Optional lifecycle hooks (`pre_generation_hook`, `post_generation_hook`) handle final
   adjustments.

______________________________________________________________________

## Runtime Customisation

Runtime hooks live in `overrides.py` and can be toggled without editing generated code:

| Environment Variable                         | Effect                                                          |
| -------------------------------------------- | --------------------------------------------------------------- |
| `RAPIDKIT_SETTINGS_EXTRA_DOTENV`             | Append extra dotenv files to the custom source chain            |
| `RAPIDKIT_SETTINGS_RELAXED_ENVS`             | Allow specified environments to bypass strict production checks |
| `RAPIDKIT_SETTINGS_ALLOW_PLACEHOLDER_SECRET` | Permit placeholder secrets when bootstrapping                   |
| `RAPIDKIT_SETTINGS_LOG_REFRESH`              | Emit structured logs whenever `Settings.refresh()` runs         |

The decorators in `overrides.py` use `core.services.override_contracts.override_method`, ensuring
the hooks remain opt-in and idempotent.

### Missing vendor snapshot — safe defaults

If a generated project does not include the vendor snapshot under
`.rapidkit/vendor/settings/<version>` (for example the user didn't `rapidkit add module settings`),
the generated runtime code will now gracefully fall back to safe default settings rather than
throwing an import error. This ensures kit-generated projects (including NestJS variants) can boot
and run out of the box while still optionally supporting the richer vendor-provided behaviours when
the `settings` module is present.

______________________________________________________________________

## Security & Audit

This module ships as part of the RapidKit module ecosystem and is intended to be **audited** as a
unit:

- Use `scripts/modules_doctor.py` (or `rapidkit modules vet`) to validate structure and generator
  invariants.
- Use `rapidkit modules verify-all` to verify recorded hashes/signatures when running in release
  mode.

If you extend this module, keep the documentation updated with the security assumptions and any
threat model relevant to your deployment.

______________________________________________________________________

## Testing Checklist

```bash
poetry run pytest tests/modules/free/essentials/settings -q

poetry run python scripts/check_module_integrity.py --module free/essentials/settings
```

______________________________________________________________________

## Release Checklist

1. Update templates and/or `module.yaml`.
1. Regenerate vendor snapshots and project variants for every supported framework.
1. Inspect rendered files (`.rapidkit/vendor` and sample project outputs) for accuracy.
1. Execute the testing checklist above; ensure versioning is bumped when content hashes change.
1. Commit regenerated assets alongside the updated metadata.

______________________________________________________________________

## Reference Documentation

- Overview: `docs/overview.md`
- Usage guide: `docs/usage.md`
- Advanced scenarios: `docs/advanced.md`
- Monitoring: `docs/monitoring.md`
- Changelog: `docs/changelog.md`
- Migration playbook: `docs/migration.md`
- Troubleshooting: `docs/troubleshooting.md`
- API reference: `docs/api-reference.md`
- Override contracts: `overrides.py`

For additional help, open an issue at <https://github.com/getrapidkit/rapidkit-core/issues> or
consult the full product documentation at <https://docs.rapidkit.top>.
