passepartout/docs/deployment.org

Deployment Guide: Containerized Org-Agent

• Overview
• Prerequisites
• Quick Start
  • 1. Build and Start
  • 2. Check Logs
• Volume Mapping
• Troubleshooting
  • signal-cli Identity
  • Re-loading Skills

Overview

The org-agent is designed to run within a Docker container to ensure system dependencies (SBCL, Quicklisp, signal-cli) are perfectly matched across different host environments.

Prerequisites

• Docker Engine
• Docker Compose
• A valid .env file in the projects/org-agent/ directory (refer to .env.example).

Quick Start

1. Build and Start

From the projects/org-agent/ directory:

docker-compose up --build -d

2. Check Logs

docker-compose logs -f

Volume Mapping

The docker-compose.yml file automatically mounts your host's memex directory to /memex inside the container. This allows the agent to:

1. Read/Write to your Zettelkasten and GTD files.
2. Maintain its local state (Object Store, snapshots).

Troubleshooting

signal-cli Identity

If using the Signal gateway, ensure you have registered your number via the host's signal-cli or within the container. The state is preserved in the signal-state Docker volume.

Re-loading Skills

The container pre-caches dependencies during the build. If you modify core Lisp logic, you must rebuild the image (--build). If you only modify .org skills in your memex, the agent can reload them dynamically if they are part of the startup scan.