Integrations overview
With DMNO you get:
- a single system to manage your config for all of your services
- secure handling of your secrets by committing them encrypted to your repo or sync with backends like 1Password
- validations, coercion logic, and full type safety
- built in documentation, and magical IDE auto-completion
- an extremely flexible type system
- live reload and re-validation on config changes
Integrations
Legend:
- ✅ Supported
- 🧰 Partially Supported
- 🚧 In Progress
- 🗓️ Planned
- ❌ Not Supported
Astro
| Feature | Description | Supported | Notes |
|---|---|---|---|
| Public Config | Access non-sensitive items | ✅ | |
| Sensitive Config | Access sensitive items | ✅ | |
| Dynamic Config | Access config items at runtime | 🧰 | |
| DMNO Types | Framework specific types from DMNO | 🗓️ | |
| Middleware | Detects leaked secrets | ✅ |
Next.js
| Feature | Description | Supported | Notes |
|---|---|---|---|
| Public Config | Access non-sensitive items | ✅ | |
| Sensitive Config | Access sensitive items | ✅ | |
| Dynamic Config | Access config items at runtime | 🧰 | |
| DMNO Types | Framework specific types from DMNO | 🗓️ | |
| Middleware | Detects leaked secrets | 🧰 |
Vite
| Feature | Description | Supported | Notes |
|---|---|---|---|
| Public Config | Access non-sensitive items | ✅ | |
| Sensitive Config | Access sensitive items | ✅ | |
| Dynamic Config | Access config items at runtime | 🧰 | |
| DMNO Types | Framework specific types from DMNO | 🗓️ | |
| Middleware | Detects leaked secrets | 🗓️ |