Can I use different secrets for development and production?

Yes, Fnox supports profiles and environment-specific files like fnox.production.toml to manage different secret sets for various stages of deployment.

What is the primary file used for Fnox configuration?

Fnox uses the fnox.toml file to define providers and secrets, with additional support for overrides in fnox.local.toml and profile-specific files.

Is it safe to commit fnox.toml to version control?

Yes, it is safe to commit fnox.toml as long as sensitive values are encrypted via a provider like 'age'. You should always gitignore your private identity keys and fnox.local.toml.

How do I validate my Fnox configuration?

You can use the 'fnox doctor' command to show diagnostic information or 'fnox provider test' to verify that specific encryption providers are working correctly.

Fnox Secrets Configuration

Name: Fnox Secrets Configuration
Author: TheBushidoCollective

byTheBushidoCollective

•

Security & Testing

Configures secure, version-controlled secrets management using the Fnox TOML schema and hierarchical file structures.

About

This skill empowers Claude to architect and maintain secure secret storage workflows using the Fnox ecosystem. It provides comprehensive guidance on initializing projects, defining encrypted secrets with the age provider, managing complex configuration hierarchies, and implementing environment-specific profiles. By leveraging this skill, developers can ensure their application secrets are handled professionally, utilizing local overrides, global settings, and validation tools to prevent common security anti-patterns like committing plain-text credentials to version control.

Key Features

Standardized TOML schema implementation for secrets
74 GitHub stars
Automated validation and diagnostics with fnox doctor
Encrypted secret definitions using age and AWS-SM providers
Hierarchical configuration management (local, project, global)
Multi-environment profile support for staging and production

Use Cases

Auditing existing configuration files for security anti-patterns and circular imports
Implementing environment-specific secret overrides for CI/CD pipelines
Setting up a new project with encrypted environment variables

About

Key Features

Standardized TOML schema implementation for secrets
74 GitHub stars
Automated validation and diagnostics with fnox doctor
Encrypted secret definitions using age and AWS-SM providers
Hierarchical configuration management (local, project, global)
Multi-environment profile support for staging and production

Use Cases

Auditing existing configuration files for security anti-patterns and circular imports
Implementing environment-specific secret overrides for CI/CD pipelines
Setting up a new project with encrypted environment variables