turnout-cli 0.22.0 → 0.23.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.
- package/README.md +6 -4
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -79,7 +79,7 @@ And see what has been going on:
|
|
|
79
79
|
|
|
80
80
|
```console
|
|
81
81
|
$ turnout status
|
|
82
|
-
turnout 0.
|
|
82
|
+
turnout 0.23.0 ~/.local/share/lacodda/turnout
|
|
83
83
|
|
|
84
84
|
Apps
|
|
85
85
|
api -> staging http://api.localhost spare :7101 (TURNOUT_GATEWAY_URL)
|
|
@@ -120,6 +120,7 @@ prod-eu · gw ok · 2 dev
|
|
|
120
120
|
- **Stays current.** A once-a-day check mentions a new release without ever delaying a command, and `self-update` installs it - leaving package-manager installs to their package manager.
|
|
121
121
|
- **One window onto it all.** `status` shows where every app points, the gateway, running jobs and the latest actions, with clickable addresses; `status --short` puts `prod · gw ok · 2 dev` into a starship or tmux line; `use -` goes back to the stand before. Every command that reports takes `--json`.
|
|
122
122
|
- **A gateway that speaks up.** A stand answering 502 or a session the stand refused shows in `status` and the prompt line, and once on the desktop - not as a mystery in your app. Stands behind single sign-on get their browser session handed over with `turnout cookie set`.
|
|
123
|
+
- **A doctor.** `turnout doctor` answers "why does it not work": a dev server left on the app's port, a dotenv file naming an old port, a stand that is down, a session that lapsed overnight, a tool missing from PATH - each with its fix, and `--fix` repairs what is turnout's to repair. `doctor --server prod` says where a deploy would stop, before it starts.
|
|
123
124
|
- **Groups.** Bind a whole contour to one stand with a single `use`.
|
|
124
125
|
- **Nothing to memorize.** Leave a name out and pick it from a list; in bash, Tab completes app, server, credential, path and group names from your own catalogs. The short alias `tn` is installed alongside.
|
|
125
126
|
- **An action journal.** Every state change appends one JSON line - what happened and to which entities, never secrets or output. `tail`, `grep` and `jq` work on it directly.
|
|
@@ -182,11 +183,12 @@ Full command reference and concepts: **[lacodda.github.io/turnout](https://lacod
|
|
|
182
183
|
|
|
183
184
|
## Status
|
|
184
185
|
|
|
185
|
-
v0.
|
|
186
|
+
v0.23.0, in daily use. Everything above works today: stands and switching
|
|
186
187
|
between them, the gateway and what it notices about them, secrets in the OS
|
|
187
188
|
keyring, the quiet console, jobs in the background with a notification when
|
|
188
|
-
they are done, `status` for a person, a prompt and a script,
|
|
189
|
-
deploy from any directory. What
|
|
189
|
+
they are done, `status` for a person, a prompt and a script, `doctor` for the
|
|
190
|
+
day something does not work, and build and deploy from any directory. What
|
|
191
|
+
landed in each version:
|
|
190
192
|
[the Releases page](https://github.com/lacodda/turnout/releases).
|
|
191
193
|
|
|
192
194
|
## Documentation
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "turnout-cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.23.0",
|
|
4
4
|
"turnout": {
|
|
5
|
-
"binary": "v0.
|
|
5
|
+
"binary": "v0.23.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",
|