steedos-builder6-config

Parse B6_ and STEEDOS_ environment variables into a nested Builder6 configuration object.

1.6k|413|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/steedos/steedos-platform --skill steedos-builder6-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steedos-builder6-config
Source: https://github.com/steedos/steedos-platform/tree/main/skills/steedos-builder6-config
Command: npx skills add https://github.com/steedos/steedos-platform --skill steedos-builder6-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builder6 server configuration is complex and error-prone when variables are scattered across env files. This Skill parses B6_ and STEEDOS_ prefixed vars into a coherent config accessible via NestJS ConfigService.

Core Features & Use Cases

  • Prefix-based parsing: automatically maps B6_ and STEEDOS_ env vars into nested config keys.
  • Required vars validation: enforces presence of critical settings like B6_MONGO_URL, B6_TRANSPORTER, B6_CACHER, B6_ROOT_URL, etc.
  • Aliases & compatibility: supports legacy MONGO_URL, ROOT_URL, PORT mappings.
  • Scope: suitable for local development, CI, and production deployments of Builder6 servers.

Quick Start

Create a .env file with the required B6_* and STEEDOS_* variables and start the Builder6 server.

Frequently Asked Questions about steedos-builder6-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize Builder6 server configuration from scattered environment variables?

Centralize Builder6 server configuration by parsing scattered environment variables into a structured configuration object using NestJS ConfigService and dotenv-flow, applying nested key mapping for database, authentication, and storage settings.

How does prefix-based parsing work for B6_ and STEEDOS_ environment variables?

Prefix-based parsing automatically maps B6_ and STEEDOS_ prefixed environment variables into nested configuration keys within a unified schema, enforcing structured mapping and startup-time validation for Node.js backends.

Does the Builder6 configuration validation support legacy compatibility aliases like MONGO_URL?

The Builder6 configuration validation supports legacy compatibility aliases, automatically mapping older variable names like MONGO_URL, ROOT_URL, and PORT to the new structured schema during environment parsing.

How do I validate required environment variables for a NestJS Builder6 backend?

Validate required environment variables for a NestJS Builder6 backend by enforcing startup-time checks for critical settings like B6_MONGO_URL, B6_TRANSPORTER, B6_CACHER, and B6_ROOT_URL to prevent missing configuration.

Can I use dotenv-flow configuration management for Builder6 across development and production scopes?

dotenv-flow configuration management suits Builder6 across local development, CI, and production scopes, parsing environment files into a coherent config accessible via NestJS ConfigService with startup-time validation.

Why does my Builder6 server fail to start when B6_ environment variables are missing?

Your Builder6 server fails to start because centralized parsing enforces required variable validation at startup, checking for critical settings like B6_MONGO_URL and B6_ROOT_URL to ensure a valid configuration object.