tiennm99
feaf4b7e4c
The entrypoint runs each vendor's installer through gosu paseo for every name in AGENT_CLIS whose command is not already on PATH, so a fresh paseo-home volume comes up with agents ready. Defaults to claude and codex; the other four are opt-in. On start rather than in the Dockerfile: Docker seeds a named volume from the image once, at creation, so a build-time install into /home/paseo would only ever reach a volume that did not exist yet. The check also chowns /home/paseo first, since a freshly created volume can arrive owned by root and the base entrypoint has not run its own chown by then. Unknown names and failed installs are logged and skipped rather than taking the container down with them. entrypoint.sh loses its explanations to the README along the way.
composes
My docker compose collection — one directory per service, each self-contained. Tuned to my own setup rather than written as general-purpose templates.
Services are deployed through Coolify and Dokploy, which own what a standalone compose file would otherwise declare:
- No published ports. The platform attaches the container to its proxy network and maps a domain to the internal port. Publishing one would also expose it on the host.
- No
restart:policy. The platform manages the container lifecycle. - No
container_name:. Compose derives it from the directory.
Services that do publish ports or set restart: say so in their own README.
Layout
<service>/
compose.yml # the service definition
README.md # what it is, its variables, how it's wired
.env.example # required variables, committed
.env # real values, gitignored
Compose names the project after its directory, so code-server/ comes up as
the code-server project with its own network and volumes.
Usage
In Coolify or Dokploy, point a Docker Compose resource at the service directory
and set the environment variables from its .env.example.
Locally:
cd <service>
cp .env.example .env # then fill it in
docker compose up -d
docker compose logs -f
docker compose down
.env is picked up automatically because it sits next to compose.yml. Never
commit it — the root .gitignore covers .env/*.env and re-includes
.env.example.
Services
Each links to its own README for variables, ports, and storage.
| Service | What it is |
|---|---|
| alloy | Grafana Alloy shipping host and Docker telemetry to Grafana Cloud |
| code-server | VS Code in the browser, as a remote dev box |
| couchbase | Couchbase Server |
| gitea-mirror-local | Gitea + PostgreSQL + gitea-mirror, mirroring GitHub repos |
| netdata | Netdata monitoring agent |
| ollama | Ollama LLM server |
| paseo | Paseo coding-agent daemon and web UI |
| traffmonetizer | TraffMonetizer bandwidth-sharing client |
Licensed under Apache 2.0 — see LICENSE.