# 🚀 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: ```bash curl -fsSL https:////multi-agent-mux/raw/branch/main/deploy/install.sh | bash ``` Alternatively, if they have cloned the repository, they can execute: ```bash 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`: ```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: 1. Ensure Gitea Actions is enabled on your Gitea instance. 2. Copy the Gitea CI workflow to your workspace's workflow folder: ```bash mkdir -p .gitea/workflows cp deploy/gitea-ci.yml .gitea/workflows/ci.yml ``` 3. 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.