Project: Homeboy

Self-improving codebase management system.

Fleet Schema

Fleet configuration defines named groups of projects stored in fleets/<id>.json. Schema { "id": "string", "project_ids": ["string"], "description": "string" } Fields Required Fields id (string): Unique fleet identifier project_ids (array of...

Cross-Compilation Guide

Homeboy can orchestrate releases for any platform, but building native binaries requires access to that platform's toolchain. What Works Anywhere Task Platform Required Version management Any Changelog operations Any Git...

Template Variables

Homeboy supports template variables in several contexts. Both single-brace ({var}) and double-brace ({{var}}) syntaxes are supported everywhere for backward compatibility. Contexts Extract Commands (extractCommand) Used in component configuration for archive...

Homeboy CLI documentation

This directory contains the markdown docs embedded into the homeboy binary and displayed via homeboy docs. Homeboy is a config-driven automation engine for development and deployment automation, with standardized patterns...

Documentation Generation

Instructions for creating comprehensive user-facing documentation from scratch by analyzing the codebase. Purpose Generate structured documentation in the /docs directory that helps end users understand and use the system. This...

Documentation Management

Homeboy provides AI agents with consistent instructions for documentation generation and maintenance. These docs serve as the single source of truth for documentation standards across all Homeboy-managed projects. Core Philosophy...

Documentation Structure

Standard patterns for organizing documentation files and directories. Directory Conventions /docs Directory User-facing documentation lives in /docs at the project root. This directory is always included in documentation scans regardless...

Component Schema

Component configuration defines buildable and deployable units stored in components/<id>.json. Schema { "id": "string", "name": "string", "local_path": "string", "remote_path": "string", "build_artifact": "string", "build_command": "string", "extract_command": "string", "version_targets": [ { "file":...

Extension Manifest Schema

Extension manifests define extension metadata, runtime behavior, platform behaviors, and integration points. Stored as <extension_id>/<extension_id>.json in the extension directory. Schema { "name": "string", "id": "string", "version": "string", "description": "string", "provides":...

Project Schema

Project configuration defines deployable environments stored in projects/<id>.json. Schema { "id": "string", "name": "string", "domain": "string", "server_id": "string", "base_path": "string", "project_type": "string", "component_ids": [], "api": {}, "database": {}, "local_environment": {},...

← Back to Chubes.net