fischermanch/aria repository overview

⁠ARIA on Docker

ARIA is a lean, modular, self-hosted AI assistant with memory, recipes, secure connections, a native tool-calling agent with MCP and controllable background jobs, and a browser-first UI.

⁠ARIA 0.1.0-alpha1007 release candidate

Alpha1007 is the reviewed candidate for the next public ARIA alpha after Alpha983. Until the owner runs the separate publish procedure, the current public image remains Alpha983.

The candidate retains the major ARIA architecture upgrade introduced in Alpha982 and the document-inventory fix from Alpha983, then adds the Activity Journal, owner-focused statistics, reliable controllable Agent Jobs, resilient MCP discovery, consistent bilingual administration and a deterministic public demo. Alpha1007 also includes the final owner-review polish for statistics and chat. The full, honest summary is in docs/release/public-release-summary-alpha1007.md.

ARIA Alpha1007 is not the same internal shape as the older public Docker Hub alpha, Alpha604.

The project has moved from the older monolith-style alpha line to a modular ARIA runtime with clearer owners for chat routing, recipes, memory, documents, notes, web/public facts, runtime actions, release/update handling, and UI composition. This is meant to make ARIA easier to maintain and safer to operate, but it also means operators should treat the next public image as an architecture migration from 0.1.0-alpha604, not as a tiny patch update.

The most important upgrade facts:

• normal managed updates recreate only aria
• Qdrant, config, prompts, notes, recipes, memory data, auth data, and volumes are not deleted or recreated by the normal update path
• current-fact and web answers now need an LLM/provider setup with web tooling or a managed web-search capability
• runtime actions, recipe execution, and target selection are more conservative and require stricter source authority, exact IDs, permissions, and confirmations
• users should prefer /updates, aria-setup upgrade, or ./aria-stack.sh update; raw Docker commands are for manual Compose installs or admin recovery

This Docker page is intentionally simple:

• one recommended install path first
• one fully manual Docker Compose path
• clear update rules for both

Repository and full documentation:

• GitHub: https://github.com/FischermanCH/A.R.I.A.
• Wiki: https://github.com/FischermanCH/A.R.I.A./wiki
• Setup docs: https://github.com/FischermanCH/A.R.I.A./tree/main/docs/setup
• Changelog: https://github.com/FischermanCH/A.R.I.A./blob/main/CHANGELOG.md
• Product Homepage: https://www.aria-agent.dev

⁠Current alpha highlights

Image tags:

• candidate immutable tag after publication: fischermanch/aria:0.1.0-alpha.1007
• moving channels: fischermanch/aria:alpha, fischermanch/aria:latest

Release highlights:

• The Activity Journal records compact, redacted summaries of completed Tool turns and Jobs without copying raw Tool output or document contents.
• Long Agent work has durable completion delivery, safe Markdown results and explicit pause, resume, correction, confirmation and cancellation controls.
• The iPhone/Safari chat stays usable in portrait and landscape, and Journal/Job/statistics timestamps follow one configurable display time zone.
• /stats restores the public Alpha983 check coverage in a clearer owner layout: concrete linked problems, visible status lamps and counts, complete Chat/embedding/web model roles, costs, activity and resources from cached/local data; opening it never calls a provider.
• MCP discovery and recipe warm-up stay out of the synchronous first-turn path; unavailable external services fail honestly without freezing chat.
• Shared bilingual page and theme rules keep the administration consistent while the graphical Memory browser remains intact.

⁠What you need

• Docker
• one long random key for Qdrant

Generate suitable values on Unix:

openssl rand -hex 32

⁠Recommended path: aria-setup

If you want the easiest install and the easiest future updates, use:

• aria-setup

It:

• asks only for the values it cannot safely guess
• creates one managed ARIA install directory
• writes a ready-to-run docker-compose.yml
• writes a matching .env
• creates visible persistent storage directories
• adds aria-stack.sh for status, logs, health, and updates
• includes aria-updater, so admin users can later start a controlled update from /updates

Managed installs also support the same controlled update flow from chat for admin users:

• zeige update status
• starte update
• bestätige update <token>

Install:

curl -fsSL https://raw.githubusercontent.com/FischermanCH/A.R.I.A./main/aria-setup -o aria-setup
chmod +x aria-setup
sudo ./aria-setup

If you already know the target values and want a fully unattended run:

sudo ./aria-setup \
  --stack-name aria-main \
  --install-dir /opt/aria/aria-main \
  --http-port 8800 \
  --public-url http://localhost:8800 \
  --non-interactive

By default this creates:

• /opt/aria/aria/docker-compose.yml
• /opt/aria/aria/.env
• /opt/aria/aria/aria-stack.sh
• /opt/aria/aria/storage/

Useful commands afterwards:

cd /opt/aria/aria
./aria-stack.sh ps
./aria-stack.sh logs
./aria-stack.sh health
./aria-stack.sh update

Managed update rules:

• normal image refresh:
  • ./aria-stack.sh update recreates only aria; Qdrant and all volumes stay untouched
• stack layout change, for example a new sidecar service:
  • aria-setup upgrade --install-dir /opt/aria/aria
• deliberate full-stack recovery:
  • ./aria-stack.sh repair or ./aria-stack.sh update-all only when release notes say so
• admin-triggered browser update:
  • /updates

The same managed update helper can also be used from chat by admin users.

Before larger upgrades, create a configuration snapshot in ARIA under:

• /config/backup

⁠Manual Docker Compose

Use this if you want to manage Compose yourself.

Use:

• docker-compose.public.yml

Do not use:

• docker-compose.yml

Reason:

• docker-compose.yml is the local repo/dev stack
• docker-compose.public.yml is the public runtime stack

⁠Manual Compose setup in 4 steps

⁠1. Create a directory

mkdir -p /opt/aria-manual
cd /opt/aria-manual

⁠2. Download the official files

curl -fsSL https://raw.githubusercontent.com/FischermanCH/A.R.I.A./main/docker-compose.public.yml -o docker-compose.yml
curl -fsSL https://raw.githubusercontent.com/FischermanCH/A.R.I.A./main/.env.example -o .env

⁠3. Edit .env

Minimum values:

ARIA_QDRANT_API_KEY=replace-with-a-long-random-key
ARIA_HTTP_PORT=8800
ARIA_PUBLIC_URL=http://localhost:8800

Optional LLM / embedding environment overrides should usually stay empty when you manage saved provider profiles inside ARIA. Only set them if you deliberately want Docker to force the live runtime values.

⁠4. Start the stack

docker compose up -d

The public manual Compose file starts:

• aria
• qdrant

The recommended managed aria-setup stack additionally starts aria-updater, so controlled UI updates do not require mounting Docker control into the application container.

Qdrant stays internal by default and is not published on host ports in the public sample.

Copy/paste-ready docker-compose.public.yml:

services:
  qdrant:
    image: qdrant/qdrant:latest
    restart: unless-stopped
    environment:
      QDRANT__SERVICE__API_KEY: ${ARIA_QDRANT_API_KEY}
    volumes:
      - qdrant_storage:/qdrant/storage

  aria:
    image: fischermanch/aria:alpha
    restart: unless-stopped
    depends_on:
      - qdrant
    ports:
      - "${ARIA_HTTP_PORT:-8800}:8800"
    extra_hosts:
      - "host.docker.internal:host-gateway"
    environment:
      ARIA_ARIA_HOST: "0.0.0.0"
      ARIA_ARIA_PORT: "8800"
      ARIA_PUBLIC_URL: ${ARIA_PUBLIC_URL:-http://localhost:8800}
      ARIA_QDRANT_URL: http://qdrant:6333
      ARIA_QDRANT_API_KEY: ${ARIA_QDRANT_API_KEY}
    volumes:
      - aria_config:/app/config
      - aria_prompts:/app/prompts
      - aria_data:/app/data
      - qdrant_storage:/qdrant/storage:ro

volumes:
  qdrant_storage:
  aria_config:
  aria_prompts:
  aria_data:

⁠Manual Compose updates

Before larger upgrades, create a configuration snapshot in ARIA under:

• /config/backup

For a normal ARIA release update:

cd /opt/aria-manual
docker compose pull aria
docker compose up -d --no-deps aria

If the release notes say the stack layout changed:

cd /opt/aria-manual
curl -fsSL https://raw.githubusercontent.com/FischermanCH/A.R.I.A./main/docker-compose.public.yml -o docker-compose.yml
docker compose up -d

Important:

• keep the same compose project
• keep the same volumes
• do not rename the stack casually between updates
• use the documented host-side docker compose commands for manual installs; the browser /updates button and chat-driven update flow are part of the managed install path
• if a managed install ever reports a mount mismatch after an update, ./aria-stack.sh repair is the supported recovery path

For multi-stack hosts or older installs pinned to a fixed image tag, the host helper can inspect and update exactly one Compose project:

docker/aria-host-update.sh detect
docker/aria-host-update.sh update --project <name> --dry-run
docker/aria-host-update.sh update --project <name> --target-image fischermanch/aria:<version>

The helper recreates only aria and preflights the intended host port before recreate. Qdrant and all volumes remain untouched. If another process already owns that port, it aborts safely before touching the running stack.

⁠Backup and recovery

ARIA includes a browser-based configuration backup under:

• /config/backup

That backup contains:

• config.yaml
• connection profiles and routing metadata
• secure-store secrets and user accounts
• prompt files
• custom recipe manifests
• error interpreter rules

It does not contain:

• memories / Qdrant collections
• chat history
• logs, uploads, or Docker stack values
• local SSH key files under data/ssh_keys

Useful chat shortcuts after setup:

• suche im internet nach rabbit r1 neuigkeiten
• zeige stats
• zeige aktivitäten
• exportiere config backup

⁠Which path should you use?

• want the easiest install and easiest updates:
  • aria-setup
• want full Docker Compose control:
  • docker-compose.public.yml

For new public installs, prefer aria-setup unless you explicitly want to manage the compose directory yourself.

⁠More

News, features, screenshots, changelog and help: www.aria-agent.dev⁠