steedos-builder6-internals

Documents Builder6 Server NestJS and Moleculer monorepo architecture and B6_* environment configuration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers working on the Builder6 Server codebase need to understand its NestJS 11 + Moleculer 0.14 hybrid monorepo structure, module organization, bootstrap sequence, and the B6_* environment variable system before they can modify or extend it safely.

Core Features & Use Cases

  • Architecture Reference: Maps the 20+ @builder6/* packages, the NestJS module tree, bootstrap middleware order, guards, and key design patterns like @InjectBroker() and DataLoader.
  • Configuration Guide: Explains how getEnvConfigs() parses B6_* and legacy STEEDOS_* variables via dotenv-flow, including type coercion and compatibility aliases like MONGO_URLB6_MONGO_URL.
  • Use Case: When adding a new NestJS module to the server, consult this Skill to place it in the right package, register it in AppModule.forRoot(), and expose its settings through properly prefixed environment variables.

Quick Start

Explain how the Builder6 Server bootstrap sequence works and which B6_* environment variables I need to configure MongoDB and Redis.

Frequently Asked Questions about steedos-builder6-internals

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

FAQPage Schema
How do I configure Builder6 Server environment variables?

Set B6_* prefixed variables such as B6_MONGO_URL, B6_PORT, and B6_JWT_SECRET, which dotenv-flow parses into nested config keys. Legacy STEEDOS_* names and aliases like MONGO_URL or PORT still work, but B6_* takes precedence.

What is the Builder6 Server monorepo structure?

It is an Nx 22 + Lerna 9 + Yarn workspace with 20+ @builder6/* packages, including server (main entry), core (auth, config, mongodb), tables, files, pages, email, moleculer, and steedos (metadata and ObjectQL).

How does NestJS integrate with Moleculer in Builder6?

The @builder6/moleculer package bridges the two frameworks. NestJS services inject the Moleculer broker via @InjectBroker(), and MoleculerModule is imported in AppModule.forRoot() alongside AuthModule and MongodbModule.

Does Builder6 Server support legacy Steedos environment variables?

Yes, compatibility aliases map legacy variables to B6_* names: MONGO_URL to B6_MONGO_URL, ROOT_URL to B6_ROOT_URL, PORT to B6_PORT, TRANSPORTER to B6_TRANSPORTER, and JWT_SECRET to B6_JWT_SECRET.

When should I use this Skill instead of the API or configuration skills?

Use it for server internals like package structure, bootstrap, middleware, and guards. For API usage refer to steedos-builder6-api, for Steedos Server internals use steedos-server-internals, and for project env config use steedos-configuration.