Refactor component terminology to programs in config and manifest
- Updated the terminology from "components" to "programs" across the codebase, including in config loading, saving, and manifest specifications. - Introduced a new `stacks.py` file to handle lifecycle actions for development stacks, implementing handlers for Python and React Vite stacks. - Adjusted tests to reflect the new program structure and ensure proper functionality. - Revised documentation to align with the new terminology and structure, ensuring clarity on the purpose and configuration of programs, services, and jobs.
This commit is contained in:
@@ -153,7 +153,7 @@ These map to two files:
|
||||
**`castle.yaml`** (in the repo, version-controlled) — Three sections:
|
||||
|
||||
```yaml
|
||||
components:
|
||||
programs:
|
||||
central-context:
|
||||
description: Content storage API
|
||||
source: components/central-context
|
||||
@@ -185,7 +185,7 @@ jobs:
|
||||
systemd: {}
|
||||
```
|
||||
|
||||
Components define *what software exists* (identity, source, install, tools).
|
||||
Programs define *what software exists* (identity, source, install, tools).
|
||||
Services define *how daemons run* (run config, expose, proxy, systemd).
|
||||
Jobs define *how scheduled tasks run* (run config, cron schedule, systemd).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user