Configure full Docker setup and confirm consequential actions

This commit is contained in:
2026-10-09 21:34:47 +01:00
parent f60599230c
commit f700d1beb2
31 changed files with 587 additions and 49 deletions
+14 -7
View File
@@ -5,24 +5,28 @@ server reuse your OpenCode login; Docker ntfy handles phone notifications.
## Install
Requires **Go 1.27+** to install. Use your existing OpenCode for model stages;
Docker/ntfy notifications are optional.
Interactive installation offers a full **Docker server + ntfy** setup (default)
or **native binaries only**. Docker mode needs Docker Compose and Python 3; native
mode needs Go 1.27+ and uses your existing OpenCode for model stages.
```sh
git clone https://git.a-wan.net/alan/pipelines.git
cd pipelines
./install.sh
./install.sh --native # host CLI/TUI/server + shared OpenCode skill
pipelines help
# Or: ./install.sh --docker # configure/start both services and connect a provider
```
Go uses `GOBIN` or its normal `GOPATH/bin` default; put that directory on PATH.
`./install.sh` installs the Go binaries and the shared OpenCode `pipelines` skill.
There are no login checks, dependency installers, hardcoded install paths, or
automatic services. With plain `go install ./cmd/...`, also run `pipelines skill install`.
Native mode installs the Go binaries and shared OpenCode `pipelines` skill without
login checks or automatic services. Docker mode configures ntfy accounts/token,
checks publishing/health, and opens container OpenCode provider login on first setup;
existing settings, credentials and volumes are retained on reinstall.
With plain `go install ./cmd/...`, also run `pipelines skill install`.
For system-wide use, install the binaries into your chosen system bin directory
with the appropriate permissions. Configuration and data remain per-user.
Start explicitly; fresh databases contain no pipelines:
Start a native server explicitly; fresh databases contain no pipelines:
```sh
pipelines serve # foreground server
@@ -132,6 +136,9 @@ conversation or intermediate stage output. Pipelines does not automatically dele
generation, agent, or formatting-repair sessions, including on failure/cancellation.
Primary session IDs are retained in run steps (`pipelines inspect <run-id> --json`).
On Home, **r** opens all recent runs; both Home panels show the shortcut.
Quit the TUI with **:quit**; **q** does not exit. **Ctrl+C** remains an interrupt.
Starting/retrying/canceling runs and deleting drafts require confirmation. CLI
publication also prompts; use `--yes` only for explicitly approved automation.
**n / :new** and creating from a template offer a Tab-navigable, fuzzy-searchable
picker: **nvim** opens the draft Markdown file; **OpenCode** authors it with you.
Canceling the picker creates no draft and publishes nothing.