57618a000e
Removes `docker/agent/Dockerfile` and `docker/workspace/Dockerfile`: - `docker/agent/Dockerfile` cloned the wrong repo (`outsourc-e/hermes-agent` is the workspace fork, not the agent) and ran the old `claude` binary name. It would not build successfully. - `docker/workspace/Dockerfile` was a dev-mode (`pnpm dev`) variant that duplicated the production root `Dockerfile` for no benefit; the dev overlay now reuses the root Dockerfile with hot-build instead. Updates `docker-compose.dev.yml` to build only the workspace from local source via the canonical root Dockerfile. The Hermes Agent service stays on the canonical `nousresearch/hermes-agent:latest` upstream image (~750k pulls), with a clear note in the overlay header explaining how to override if a custom agent image is genuinely needed. Adds a quick-start path table at the top of README pointing 'compose gig' users straight at the Docker section, and rewrites the dev-overlay section to match the simpler reality. This addresses the recurring 'can we get a docker image so I can set up a compose gig instead of building from source' community ask. The image already exists at `ghcr.io/outsourc-e/hermes-workspace:latest`, the compose file just works \u2014 the stale local Dockerfiles were the only thing making the dev overlay confusing. Co-authored-by: Aurora release bot <release@outsourc-e.com>
27 lines
1.1 KiB
YAML
27 lines
1.1 KiB
YAML
# Hermes Workspace — Development Overlay
|
|
#
|
|
# Builds the Workspace image from local source instead of pulling the
|
|
# pre-built GHCR image. Use when iterating on Workspace code (server,
|
|
# routes, UI) and you want changes to land in the container without
|
|
# publishing a release first.
|
|
#
|
|
# The Hermes Agent service still uses the canonical upstream image
|
|
# (nousresearch/hermes-agent:latest, ~750k pulls) — there is no need to
|
|
# rebuild that locally, and doing so just couples the compose stack to
|
|
# whatever vendored Python the workspace happens to ship. If you really
|
|
# need a custom agent image, build/tag it separately and override the
|
|
# `image:` field in your own .override.yml.
|
|
#
|
|
# Usage:
|
|
# docker compose -f docker-compose.yml -f docker-compose.dev.yml up --build
|
|
#
|
|
# The base docker-compose.yml stays untouched for a regular install-and-run.
|
|
# When this overlay is merged in, `build:` takes priority over `image:` for
|
|
# the workspace service so local source is compiled instead of pulled.
|
|
|
|
services:
|
|
hermes-workspace:
|
|
build:
|
|
context: .
|
|
dockerfile: ./Dockerfile
|