turnout-cli 0.18.0 → 0.20.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +16 -10
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -32,10 +32,15 @@ Start working, from wherever you happen to be:
32
32
 
33
33
  ```console
34
34
  $ cd ~/dev/web/src/components
35
- $ turnout dev
36
- [web] pnpm dev
35
+ $ turnout dev --open
36
+ [web] pnpm dev --port 5100
37
+ [web] http://web.localhost -> dev server port 5100
38
+ ◇ web ready in 1.4s - http://web.localhost
37
39
  ```
38
40
 
41
+ The server is up, the page is open, and the console stays quiet from here -
42
+ until something breaks, which is when you want it loud.
43
+
39
44
  Move the whole contour at once when the frontend and the API must agree:
40
45
 
41
46
  ```console
@@ -74,7 +79,7 @@ And see what has been going on:
74
79
 
75
80
  ```console
76
81
  $ turnout status
77
- turnout 0.18.0
82
+ turnout 0.20.0
78
83
  Data directory: ~/.local/share/lacodda/turnout
79
84
  Apps: 2 (api, web)
80
85
  Servers: 2 (prod-eu, staging)
@@ -88,6 +93,7 @@ Bindings:
88
93
  Gateway: running (pid 24180)
89
94
  Front: http://localhost - http://NAME.localhost
90
95
  Spare: web:7100 -> VITE_API_URL, api:7101 -> TURNOUT_GATEWAY_URL
96
+ Jobs: 2 running (api dev, web dev) - see `turnout ps`
91
97
  Recent:
92
98
  2026-08-09T01:15:02Z deploy web -> prod-eu (142 files)
93
99
  2026-08-09T01:12:44Z use web -> prod-eu
@@ -104,6 +110,8 @@ Recent:
104
110
  - **The SSH agent signs for you.** A credential can authenticate with a key the agent already holds unlocked, so a passphrase is typed once per login session instead of once per command - turnout never reads the key file at all. `SSH_AUTH_SOCK` on Linux and macOS; on Windows, Pageant or the OpenSSH agent service, whichever is running. An agent holding several keys is the normal case: they are offered in turn and the first the server accepts wins.
105
111
  - **Secrets in the OS keyring** - Windows Credential Manager, macOS Keychain, Linux Secret Service. A secret belongs to a credential, so one `pass set` covers every stand that credential reaches. Copy it to the clipboard with one command; nothing lands in a config file, and `status` only ever reports *that* a credential exists.
106
112
  - **Commands from any directory.** `dev`, `build`, `test`, `lint` and any custom command run in the right project folder. Commands are taken from your actual `package.json` scripts, so a project whose dev script is `serve` still answers to `turnout dev`.
113
+ - **A quiet console.** A build shows a loader and its elapsed time, not two minutes of scrollback; a dev server goes quiet once it reports itself and speaks again only when something breaks. A failure prints its output on the spot - no re-run to see what went wrong - and every job's output is kept in a log file whatever the terminal showed. `-v` gives you all of it, and so does any pipe, so scripts and CI logs are unchanged.
114
+ - **Jobs in the background.** `turnout dev --detach` gives the terminal back and the server keeps running; so do `build`, `run` and `deploy`. `turnout ps` shows everything turnout runs - the gateway included - with ports, addresses and uptime, `logs -f` follows any of it, and `stop` takes a job down with every process it started.
107
115
  - **A hand on the server.** `turnout ssh web-prod` opens a session with host, port, user and key from the catalogs, in the deploy directory, the password already on the clipboard; `turnout exec web-prod -- docker compose ps` runs one command there and hands back its exit code.
108
116
  - **Deploy over SSH/SFTP** - build, upload, restart, with remote backup and restore when a release goes wrong. Artifacts travel as a single archive instead of thousands of round trips, falling back to file-by-file when the server cannot unpack one. Linux and Windows servers alike: turnout detects which shell answers SSH and phrases every remote command in it.
109
117
  - **Portable settings.** `export` writes your apps, servers, credentials, paths, targets and groups to one file and `import` merges it on another machine; secrets come along only when you ask, sealed with a passphrase.
@@ -170,13 +178,11 @@ Full command reference and concepts: **[lacodda.github.io/turnout](https://lacod
170
178
 
171
179
  ## Status
172
180
 
173
- Everything above works today. What is next:
174
-
175
- - [ ] **Background runs** - `dev --detach`, `ps`, `logs`, `stop`, OS notifications
176
- - [ ] **Observability** - gateway request log, `doctor`, `report` for handing context to an assistant
177
- - [ ] **Deploy consists** - atomic deploy and rollback across a group of apps
178
-
179
- Released versions and what landed in each: [CHANGELOG on the Releases page](https://github.com/lacodda/turnout/releases).
181
+ v0.20.0, in daily use. Everything above works today: stands and switching
182
+ between them, the gateway, secrets in the OS keyring, the quiet console, jobs
183
+ in the background with `ps`, `logs` and `stop`, and build and deploy from any
184
+ directory. What landed in each version:
185
+ [the Releases page](https://github.com/lacodda/turnout/releases).
180
186
 
181
187
  ## Documentation
182
188
 
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "turnout-cli",
3
- "version": "0.18.0",
3
+ "version": "0.20.0",
4
4
  "turnout": {
5
- "binary": "v0.18.0"
5
+ "binary": "v0.20.0"
6
6
  },
7
7
  "description": "A developer's switchyard: point local apps at any backend stand, keep servers and secrets at hand, build and deploy from any directory",
8
8
  "license": "MIT",