
osac-project/osac-workspace
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
Workspace for operating on OSAC repositories with AI tooling
Обзор
Do not start a new osac-workspace checkout. Clone osac-project/osac and run tools/bootstrap.sh there. Do not run osac/tools/bootstrap.sh from osac-workspace/osac. Development workspace for the Open Sovereign AI Cloud (OSAC) project. This repo provides a meta-workspace that bootstraps all OSAC components for cross-component development and testing, with AI-assisted workflows for Claude Code, Cursor, and Gemini CLI. Choose one of the two development setups: All dev tools are packaged in a container — no need to install toolchains on your host. See Distrobox Dev Environment to get started. - - : Install and authenticate with gh auth login (required for fork workflow; use --no-fork if you only need read-only access) - Go, Node.js, buf, kubectl, kind, jira CLI (see Setup for details) New work should use a standalone osac clone and tools/bootstrap.sh there (see the notice above). The bootstrap script clones all OSAC repos into the workspace.
README
Показан фрагмент оригинального README. Открыть оригинал.
OSAC Project
[!IMPORTANT] New work is in osac-project/osac. Do not start a new osac-workspace checkout. Clone
osac-project/osacand runtools/bootstrap.shthere. Do not runosac/tools/bootstrap.shfromosac-workspace/osac.
Development workspace for the Open Sovereign AI Cloud (OSAC) project. This repo provides a meta-workspace that bootstraps all OSAC components for cross-component development and testing, with AI-assisted workflows for Claude Code, Cursor, and Gemini CLI.
Prerequisites
Choose one of the two development setups:
Option A: Distrobox (recommended)
All dev tools are packaged in a container — no need to install toolchains on your host.
See Distrobox Dev Environment to get started.
Option B: Local toolchain
Install tools directly on your host.
- git
- gh CLI: Install and authenticate with
gh auth login(required for fork workflow; use--no-forkif you only need read-only access) - Go, Node.js, buf, kubectl, kind, jira CLI (see Setup for details)
Getting Started
New work should use a standalone osac clone and tools/bootstrap.sh there (see the notice above).
Existing osac-workspace checkout
cd /path/to/osac-workspace
./bootstrap.sh
# Or update read-only without forking
./bootstrap.sh --no-fork
The bootstrap script clones all OSAC repos into the workspace. Each repo is an independent Git repository on its main branch. By default, remotes are named origin (upstream) and fork (push target). Use --fork-name to choose a different push remote name (e.g., --fork-name origin for the conventional layout where origin is your fork and upstream is the project repo).
resolve-remotes.sh (vendored via osac-ai-skills, at ~/.osac-ai-skills or ./.osac-ai-skills) detects remotes by URL, so all skills and hooks work regardless of naming.
Use --no-fork if you only need read-only access or are running in CI. To override fork repo names (e.g., if your fork of docs is named osac-docs), copy fork-overrides.sh.example to fork-overrides.sh and edit it.
Legacy: clone this workspace
Only if you already depend on the meta-workspace layout:
git clone https://github.com/osac-project/osac-workspace.git
cd osac-workspace
./bootstrap.sh
Components
| Component | Description |
|---|---|
| osac | Mono-repo: fulfillment-service + osac-operator + osac-aap + osac-installer + bare-metal-fulfillment-operator + osac-csi-driver (see subdirectories below) |
osac/fulfillment-service |
gRPC/REST API server with PostgreSQL backend — manages VirtualNetworks, Subnets, SecurityGroups, ComputeInstances |
Рекомендуемые инструменты
Попробуйте другой запрос или уберите фильтр.
Установка
npx skillfish add osac-project/osac-workspace