Configure full Docker setup and confirm consequential actions
This commit is contained in:
+14
-1
@@ -1,5 +1,18 @@
|
||||
# Pipeline server + ntfy in one Compose project (Android)
|
||||
|
||||
## Complete installer (recommended for both services in Docker)
|
||||
|
||||
Run `./install.sh --docker` from an interactive terminal. It handles Compose
|
||||
configuration, ntfy users/permissions/token, image build, container skill install,
|
||||
first-time container OpenCode provider login, startup, and an authenticated test
|
||||
notification. Choose your own provider in OpenCode; signup/login credentials stay
|
||||
in the Docker volume, not your host OpenCode account. Re-run to update while
|
||||
preserving `.env`, tokens, histories and volumes. Use `--relogin` to connect another
|
||||
provider. No fixed OpenCode Go login is required. Health/publishing checks do not
|
||||
prove model inference or phone reception.
|
||||
|
||||
The steps below are for manual setup or a local Pipelines server with Docker ntfy.
|
||||
|
||||
## Local pipeline server, Docker ntfy
|
||||
|
||||
To reuse your host OpenCode login without container authentication:
|
||||
@@ -91,7 +104,7 @@ docker compose up -d
|
||||
docker compose logs -f pipelines
|
||||
```
|
||||
|
||||
Select **OpenCode Go** and follow its authentication flow. Credentials are stored
|
||||
Select your preferred provider and follow its authentication flow. Credentials are stored
|
||||
in the dedicated `opencode-home` volume, separate from your host account. These
|
||||
container commands are **not tested** here. The image includes Go/git for the
|
||||
existing narrowly approved verification tools; the actual server runs as uid 10001.
|
||||
|
||||
Reference in New Issue
Block a user