Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
# Homelab-specific deploy configuration.
#
# Copy this file to `bin/deploy.env` and fill in your values. The real
# `bin/deploy.env` is gitignored — never commit it.
# SSH target (user@host or just host if you've set it up in ~/.ssh/config).
SERVER="[email protected]"
# Absolute path on the homelab where docker-compose.yml + .env.production live.
# The deploy script runs `docker compose pull/down/up` inside this dir.
DEPLOY_DIR="/var/opt/docker/utils/ai-memory"
# Image tag to build + push + pull. Make sure the Docker host can pull
# from wherever you push to (Docker Hub, GHCR, your own registry).
#
# Use a tag of your OWN, not a release tag. `bin/deploy` builds for the
# architecture of the machine you run it on; pushing that over `:latest`
# or `:X.Y.Z` — which CI publishes as multi-arch manifests — drops every
# other architecture and breaks those hosts with "exec format error"
# (issue #427). bin/deploy refuses to do it, but pick a private tag here
# and there is nothing to refuse.
IMAGE="akitaonrails/ai-memory:homelab"
# If you only want to run the RELEASED image rather than build your own,
# you do not need bin/deploy at all — point docker-compose.yml at
# `akitaonrails/ai-memory:latest` on the server and run:
# docker compose pull && docker compose up -d
# Optional: override the container name if your docker-compose.yml
# uses something other than the default `ai-memory`.
# CONTAINER_NAME="ai-memory"