| .. | ||
| .gitkeep | ||
| create-installer.nu | ||
| docs_discovery.nu | ||
| docs_postprocessing.nu | ||
| docs_templates.nu | ||
| generate-distribution.nu | ||
| generate-docs.nu | ||
| guide_generators.nu | ||
| installer_generator.nu | ||
| installer_metadata.nu | ||
| installer_utilities.nu | ||
| installer_validator.nu | ||
| platform_compiler.nu | ||
| prepare-core-dist.nu | ||
| prepare-platform-dist.nu | ||
| README.md | ||
| test_min2.nu | ||
Distribution Package Generation
Purpose: Generate complete distribution packages from compiled binaries and libraries.
Contents
Scripts and outputs for creating distribution-ready packages across multiple platforms and formats.
What is Distribution Generation
Distribution generation takes the compiled artifacts from dist/ and packages them into:
- Installable archives (tar.gz, zip)
- Platform-specific installers (deb, rpm, brew)
- Docker/container images
- Binary distributions with configuration templates
Build Process
The distribution build system:
- Takes binaries from
dist/platform/ - Takes libraries from
dist/core/ - Takes configuration templates from
dist/config/ - Combines with installation scripts
- Creates platform-specific packages
Generate a distribution:
just dist-generate # Full distribution generation
just dist-validate # Validate generated distribution
Output Artifacts
Generated distribution includes:
- Compiled binaries (orchestrator, control-center, MCP server)
- Installation script (install.sh)
- Configuration templates
- Documentation
- License files
Related Directories
dist/- Build output (source for distribution)package/- Alternative packaging (low-level format creation)release/- Version management and release tagging
Integration
The distribution output is used by:
- Installation system (
provisioning-installer) - Package managers
- CI/CD pipelines
- End-user downloads