Files
Triple-C/container/mission-control/projects.md.template
Josh Knapp 2dffef0767
All checks were successful
Build App / compute-version (push) Successful in 2s
Build App / build-macos (push) Successful in 2m47s
Build Container / build-container (push) Successful in 9m0s
Build App / build-linux (push) Successful in 4m41s
Build App / build-windows (push) Successful in 5m33s
Build App / create-tag (push) Successful in 3s
Build App / sync-to-github (push) Successful in 10s
Bundle mission-control into Triple-C instead of cloning from GitHub
The mission-control (Flight Control) project is being closed upstream.
This embeds the project files directly in the repo under container/mission-control/,
bakes them into the Docker image at /opt/mission-control, and copies them into place
at container startup instead of git cloning from GitHub.

Also adds missing osc52-clipboard, audio-shim, and triple-c-sso-refresh to the
programmatic Docker build context in image.rs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-03 09:09:15 -07:00

30 lines
701 B
Plaintext

# Projects Registry
This file catalogs all active projects to provide context for mission, flight, and leg planning.
Copy this file to `projects.md` and fill in your project details.
---
## example-project
**Description**: Brief description of what this project does.
| Property | Value |
|----------|-------|
| Path | `/path/to/project` |
| Remote | `git@github.com:username/repo.git` |
| Stack | (optional) Key technologies used |
| Status | (optional) Current state of the project |
---
## another-project
**Description**: Another project description.
| Property | Value |
|----------|-------|
| Path | `/path/to/another-project` |
| Remote | `git@github.com:username/another-repo.git` |