turnout-cli 0.4.1 → 0.5.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 +4 -3
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -74,7 +74,7 @@ And see what has been going on:
|
|
|
74
74
|
|
|
75
75
|
```console
|
|
76
76
|
$ turnout status
|
|
77
|
-
turnout 0.
|
|
77
|
+
turnout 0.5.0
|
|
78
78
|
Data directory: ~/.local/share/lacodda/turnout
|
|
79
79
|
Apps: 2 (api, web)
|
|
80
80
|
Servers: 2 (prod-eu, staging)
|
|
@@ -94,7 +94,9 @@ Recent:
|
|
|
94
94
|
- **A dev gateway.** Apps always talk to `localhost`; turnout forwards to the selected stand over HTTP or HTTPS (self-signed certificates allowed per server), rewrites redirects, proxies WebSockets, and keeps a cookie jar per app+stand pair so switching does not log you out.
|
|
95
95
|
- **Secrets in the OS keyring** - Windows Credential Manager, macOS Keychain, Linux Secret Service. Copy a password to the clipboard with one command; nothing lands in a config file, and `status` only ever reports *that* a credential exists.
|
|
96
96
|
- **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`.
|
|
97
|
-
- **Deploy over SSH/SFTP** - build, upload, restart, with remote backup and restore when a release goes wrong.
|
|
97
|
+
- **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.
|
|
98
|
+
- **Portable settings.** `export` writes your apps, servers and groups to one file and `import` merges it on another machine; secrets come along only when you ask, sealed with a passphrase.
|
|
99
|
+
- **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.
|
|
98
100
|
- **Groups.** Bind a whole contour to one stand with a single `use`.
|
|
99
101
|
- **Nothing to memorize.** Leave a name out and pick it from a list; in bash, Tab completes app, server and group names from your own catalogs. The short alias `tn` is installed alongside.
|
|
100
102
|
- **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.
|
|
@@ -149,7 +151,6 @@ Full command reference and concepts: **[lacodda.github.io/turnout](https://lacod
|
|
|
149
151
|
|
|
150
152
|
Everything above works today. What is next:
|
|
151
153
|
|
|
152
|
-
- [ ] **Updates and portability** - update notice, `self-update`, `export` / `import` for moving to another machine
|
|
153
154
|
- [ ] **Credentials and paths as their own entities** - one login reused across servers, a remote directory declared once, and named builds so a deploy stays a single word
|
|
154
155
|
- [ ] **Background runs** - `dev --detach`, `ps`, `logs`, `stop`, OS notifications
|
|
155
156
|
- [ ] **Observability** - gateway request log, `doctor`, `report` for handing context to an assistant
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "turnout-cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.5.0",
|
|
4
4
|
"turnout": {
|
|
5
|
-
"binary": "v0.
|
|
5
|
+
"binary": "v0.5.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",
|