What problem does it solve?
TGDB users need a consistent, low-risk way to integrate a new containerized project into TGDB, while choosing the correct integration path (AppSpec vs advanced module) and ensuring rootless/rootful compatibility.
Core Features & Use Cases
- Integration route decision (AppSpec vs advanced app): Determines whether the project fits TGDB AppSpec (menu 6) or should be implemented as an advanced application (menu 7) based on operational complexity and maintainability.
- Rootless vs rootful deployment planning: Recommends default and compatibility settings using explicit rules for host networking, privileged mounts, low ports, and sensitive host resources.
- Upstream-to-TGDB specification mapping: Extracts required deployment information (image/tag or build instructions, ports, env vars, volumes, init/migrate/seed needs) and turns it into TGDB-ready artifacts.
- Implementation guidance + smoke-test verification: Produces concrete file changes (app.spec, quadlet units, env/config templates, optional build scripts) and runs validation checks to ensure the app is discoverable and renderable.
Quick Start
Ask: "Evaluate this project for TGDB integration and implement the necessary TGDB files and validation for it."