drop2run 0.6.0 → 0.8.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 +8 -3
- package/dist/index.js +917 -86
- package/dist/{package-bzaCMW_E.js → package-BycuI1VJ.js} +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -22,6 +22,11 @@ drop2run init|deploy --folder <path> File the new site in one of your fo
|
|
|
22
22
|
drop2run ls List your sites
|
|
23
23
|
drop2run folders List your folders, as --folder takes them
|
|
24
24
|
drop2run open [site] Open a site in a browser
|
|
25
|
+
drop2run info [site] Show a site's settings and versions
|
|
26
|
+
drop2run set <setting> <value> [--site X] Change one setting
|
|
27
|
+
drop2run unset name|password|expires Clear a name, a password or a takedown
|
|
28
|
+
drop2run pause [site] Take a site off the air, keeping its files
|
|
29
|
+
drop2run resume [site] Put a paused site back on the air
|
|
25
30
|
drop2run rollback <deployId> [--site X] Put an earlier version back live
|
|
26
31
|
drop2run rm <site> --yes Delete a site and everything on it
|
|
27
32
|
drop2run token list List your access tokens
|
|
@@ -82,7 +87,7 @@ server on `127.0.0.1`, which is what keeps it out of clipboards and scrollback.
|
|
|
82
87
|
|
|
83
88
|
### `--device`, for a machine with no browser
|
|
84
89
|
|
|
85
|
-
`drop2run login --device` prints a short code and waits. Enter it at <https://dropto.run/device> from any
|
|
90
|
+
`drop2run login --device` prints a short code and waits. Enter it at <https://app.dropto.run/device> from any
|
|
86
91
|
machine you are already signed in on — a phone will do — and the terminal picks up its token.
|
|
87
92
|
|
|
88
93
|
The short code is not the credential; it names the pending request, so somebody reading it over your
|
|
@@ -92,7 +97,7 @@ works once.
|
|
|
92
97
|
### CI
|
|
93
98
|
|
|
94
99
|
Neither flow works in CI — nothing there can open a browser or approve anything. Create a token at
|
|
95
|
-
<https://dropto.run/account/tokens> and set it in the environment:
|
|
100
|
+
<https://app.dropto.run/account/tokens> and set it in the environment:
|
|
96
101
|
|
|
97
102
|
```
|
|
98
103
|
DROP2RUN_TOKEN=d2r_...
|
|
@@ -110,7 +115,7 @@ account" is answerable in an issue report or a CI log.
|
|
|
110
115
|
|
|
111
116
|
Both need a browser session, and that is deliberate rather than missing. A token that can mint tokens is
|
|
112
117
|
not a leaked credential but a permanent one: whoever takes it makes a second, and revoking the first
|
|
113
|
-
changes nothing. Make and revoke tokens at <https://dropto.run/account/tokens>.
|
|
118
|
+
changes nothing. Make and revoke tokens at <https://app.dropto.run/account/tokens>.
|
|
114
119
|
|
|
115
120
|
`token list` does exist and answers what a terminal can answer — which machines hold a credential, and
|
|
116
121
|
which of them has not used it since it was made. It prints prefixes, never secrets.
|