astral/kuber
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: release 2.7.0-rc3

Browse Source
This commit is contained in:
dmgnr
2026-10-07 05:10:59 +00:00 Unverified
parent c8de9ddcba
commit 2a24b2ff56
14 changed files with 1302 additions and 249 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+40 -16
View File
@@ -67,6 +67,13 @@ https://kuber.astrxl.dev/api/v2
## Authentication
`kuber login [username] [--persist]` opens an interactive BasicAuth prompt for
the password (the optional username pre-fills the username field). Commands
that need authentication, including `init`, log in this way when no session is
available; `init` also retries login if the server reports an expired or
unauthorized session. Login requires an interactive terminal when credentials
are needed.
```bash
kuber login dmgnr
kuber login dmgnr --persist
@@ -468,7 +475,10 @@ replay the command; rerun it yourself if needed.
`kuber init` creates a project Compose file and adds its first app. In an empty
directory, the default app uses `nginx:stable` as its image; initialization
always adds a service. Choose a different source or image with the app options:
always adds a service. With an interactive terminal, the first prompt selects
the app source. The selected source then determines which follow-up fields are
shown: an image URI for `image`, a CNB buildpack URI for `auto`, or an embedded
Dockerfile template for `template`.
```bash
kuber init
@@ -476,12 +486,19 @@ kuber init --project my-site --name web --path apps/web --source image --image n
```
With an interactive terminal, `init` prompts for missing project and app
details, and its default flow logs in automatically when needed. The project
trust is granted for the current directory as part of initialization, so a
first `kuber up` can proceed without separately running `kuber trust`. Use
`--non-interactive` to disable prompts; provide required values as flags. The
project name is optional and defaults from the current project context. If
project configuration already fixes a project name, `--project` must match it.
details. If multiple app roots are detected, an AutoComplete prompt lets you
choose the app path; pass `--path` to select one directly. A YAML Snippet prompt
then edits the project, service, claims, resources, and replica count together;
the replica count defaults to `1`. Blank optional values are omitted from the
generated configuration. The `managedBy` documentation header is added when the
Compose file is written. Initialization logs in automatically when needed and
trusts the current directory for the selected project, so a first `kuber up`
does not require a separate `kuber trust`.
Use `--non-interactive` to disable prompts and provide the required values as
flags. The project name is optional and defaults from the current project
context. If project configuration already fixes a project name, `--project`
must match it.
`kuber add app` adds another service to an existing project without replacing
existing services. Its syntax and the shared app options are:
@@ -503,15 +520,22 @@ For example, add an app using a published starter image:
kuber add app --name web --path apps/web --source image --image nginx:stable --non-interactive
```
In interactive mode, omitted values are prompted for. The app path is chosen
from detected app roots when there is exactly one; when there are several, the
prompt asks you to select one. Supply `--path` to select a subproject explicitly.
Non-interactive mode never prompts: supply values needed for the selected
source, and for multiple detected roots explicitly supply `--path`. With no
detected app roots the path defaults to `.`. If no source is supplied, a
repository with detected app roots defaults to `auto`; otherwise it defaults to
`image` (`nginx:stable`). Optional Postgres/S3 claims and CPU, memory, and
replica settings can be provided by flags or interactively.
In interactive mode, the first prompt selects the app source, followed by
source-specific input: an image URI, a CNB buildpack URI, or a Dockerfile
template. When multiple app roots are detected, an AutoComplete prompt selects
the path; with one detected root it is selected automatically. A YAML Snippet
prompt edits the service, claims, resources, and replicas (default `1`) in
`compose.yml`. Existing services are presented literally as `name: ...` and
remain read-only while the new service is configured. Blank optional values
are omitted when the Compose YAML is written. The `managedBy` documentation
header is added to the written file.
`--non-interactive` retains the no-prompt behavior: supply values needed for
the selected source, and for multiple detected roots explicitly supply
`--path`. With no detected app roots the path defaults to `.`. If no source is
supplied, a repository with detected app roots defaults to `auto`; otherwise it
defaults to `image` (`nginx:stable`). Optional Postgres/S3 claims and CPU,
memory, and replica settings can be provided by flags or interactively.
#### App sources