Files

T

Godopu 387b43d8e3 fix(deploy): stage installer download and copy runtime assets no-clobber (FW-D1)

deploy/install.sh extracted the repo archive in-place with
`tar --strip-components=1`, which inside an existing project could silently
overwrite the target's own README.md/FUTURE_WORKS.md/etc and litter it with
this repo's dev docs.

Rebuild the fetch path:
- stage the clone/extract into a `mktemp -d` dir, never in-place
- verify `.agents/skills/lib.sh` is present before copying anything
- copy only runtime assets (.agents/, AGENT.md, .env.example) into the target
  with per-file no-clobber guards (`[ ! -e ]`), so existing files always win
- post-fetch sanity check now tests a file, not just the directory
- fail fast when neither git nor curl is available

Use explicit `[ ! -e ]` guards + a POSIX find merge rather than `cp -n`
(non-portable; emits a deprecation warning on GNU coreutils 9.x). The earlier
`tar --exclude` denylist idea was rejected in review: non-portable and the
unanchored `--exclude="scripts"` pattern stripped the skills' own nested
scripts/ dirs, yielding a silently broken install.

Mark FW-D1 resolved and FW-D2 partially addressed in FUTURE_WORKS.md/.ko.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-24 10:33:05 +09:00

gitea-ci.yml

feat(deploy): add Gitea deployment templates, installer, and CI/CD workflow

2026-06-23 08:22:41 +09:00

install.sh

fix(deploy): stage installer download and copy runtime assets no-clobber (FW-D1)

2026-06-24 10:33:05 +09:00

plugin.json

feat(deploy): add Gitea deployment templates, installer, and CI/CD workflow

2026-06-23 08:22:41 +09:00

README.md

fix(deploy): automatically download .agents/skills from Gitea if missing in installer

2026-06-23 23:16:00 +09:00

README.md

🚀 Multi-Agent Mux (MAM) Deployment & Gitea Integration

This directory contains packaging templates and installation scripts to deploy the Multi-Agent Mux framework into workspaces hosted on Gitea (or GitHub).

📁 Deployment Directory Structure

install.sh: A self-contained, idempotent shell installer that checks system requirements (tmux, python3, pip3), detects NFS/network filesystem mounts, sets up a local python virtual environment (.venv), and initializes environment configuration (.env).
plugin.json: Metadata declaration file to register MAM as an installable plugin for AI Agent coding platforms (such as Claude Code, Antigravity, or other TUI clients).
gitea-ci.yml: CI/CD pipeline definition template for Gitea Actions (running ShellCheck linting on bash scripts, validation on python scripts, and compilation tests).

📦 How to Install and Deploy

1. Simple One-Liner Installation (from Gitea repository)

Once you push this repository to your Gitea instance, users can install it in their local workspace directory by running:

curl -fsSL https://git.godopu.com/tmpl/multi-agent-mux/raw/branch/main/deploy/install.sh | bash

Alternatively, if they have cloned the repository, they can execute:

bash deploy/install.sh

2. Registering as a Workspace Plugin

To register these skills globally or for a specific workspace:

Workspace Level: Copy the .agents/ folder into your project root.
Global Level (Gemini/Antigravity): Register the plugin path in your global config file at ~/.gemini/config/skills.json:
```
{
  "entries": [
    { "path": "/absolute/path/to/multi-agent-mux/.agents/skills" }
  ]
}
```

🤖 Gitea Actions CI/CD Setup

To automate testing and script linting on your Gitea repository:

Ensure Gitea Actions is enabled on your Gitea instance.

Copy the Gitea CI workflow to your workspace's workflow folder:

mkdir -p .gitea/workflows
cp deploy/gitea-ci.yml .gitea/workflows/ci.yml

Commit and push to your Gitea repository. The pipeline will validate shell syntax and python file compilation on every push to main and pull requests.