forked from molecule-ai/molecule-core
bd145dcec6
The molecule-ai-workspace-runtime mirror is regenerated on every
runtime-v* tag from this monorepo's workspace/. Per saved memory
reference_runtime_repo_is_mirror_only, mirror-guard rejects direct
PRs to the mirror; edit at source.
Source-side files that propagate to the mirror's published README +
read by users of the in-monorepo workspace-runtime docs:
- scripts/build_runtime_package.py (the README generator):
* line 281 README_TEMPLATE: 'Shared workspace runtime for Molecule
AI' link → Gitea
* line 399 doc-link to workspace-runtime-package.md → Gitea path
(with /src/branch/main/ shape)
LEFT AS-IS (per Q3 audit-trail decision):
* lines 379, 392 historical issue cross-refs (#2936, #2937)
- workspace/build-all.sh:5 — comment block linking to template-*
repos. Migrated to Gitea path-shape.
- docs/workspace-runtime-package.md:
* lines 101-108 adapter→repo table (8 templates, all PUBLIC on
Gitea) — Gitea URLs
* line 247 starter-repo link — substituted host + added inline
note that starter doesn't survive the suspension migration
(recreation pending; cross-link to this issue)
* line 259 generic git clone command for new templates → Gitea
* line 289 second starter mention — same handling as 247
Files NOT touched in this PR:
- workspace/ Python source code (.py files) — those use github
paths in docstrings + a few log strings; fix bundled with the
cross-repo Go-module-style migration (per #37 Q5 + parked
follow-ups).
- 'Writing a new adapter' section's `gh repo create` command (line
254-256) — gh CLI doesn't talk to Gitea (per #45 parked follow-up).
- 'Writing a new adapter' section's ghcr.io image ref (line 276) —
per #46 ghcr→ECR migration (separate concern).
After this PR merges to staging + a runtime-v* tag is pushed, the
mirror's published README will inherit the Gitea link. Until then
the mirror's README continues to reference github.com/Molecule-AI
(stale but historical-marker-correct since the mirror existed
pre-suspension).
Refs: molecule-ai/internal#41, molecule-ai/internal#37,
molecule-ai/internal#38, molecule-ai/internal#42,
molecule-ai/internal#45, molecule-ai/internal#46
38 lines
1.3 KiB
Bash
Executable File
38 lines
1.3 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# build-all.sh — Rebuild base image and optionally adapter images.
|
|
#
|
|
# NOTE: Adapters have been extracted to standalone template repos:
|
|
# https://git.moleculesai.app/molecule-ai/molecule-ai-workspace-template-<runtime>
|
|
#
|
|
# This script now only builds the base image from workspace/Dockerfile.
|
|
# Each adapter repo has its own Dockerfile that installs molecule-ai-workspace-runtime
|
|
# from PyPI and the adapter-specific deps.
|
|
#
|
|
# Usage:
|
|
# bash workspace/build-all.sh # Build base image only
|
|
#
|
|
# Standalone adapter repos still reference the legacy base image for local dev
|
|
# (e.g. FROM workspace-template:base). To build those locally, clone the adapter
|
|
# repo and run `docker build -t workspace-template:<runtime> .` from its root.
|
|
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
|
|
cd "$SCRIPT_DIR"
|
|
|
|
GREEN='\033[0;32m'
|
|
RED='\033[0;31m'
|
|
NC='\033[0m'
|
|
|
|
log() { echo -e "${GREEN}[build]${NC} $1" >&2; }
|
|
err() { echo -e "${RED}[error]${NC} $1" >&2; }
|
|
|
|
# Build base image
|
|
log "Building workspace-template:base ..."
|
|
if ! docker build -t workspace-template:base -f Dockerfile . ; then
|
|
err "Base image build failed"
|
|
exit 1
|
|
fi
|
|
log "Base image built"
|
|
log "Done. Adapters are in standalone template repos — see docs/workspace-runtime-package.md"
|