nukebase 2.4.0 → 2.5.1

package/README.md

@@ -24,7 +24,7 @@ nukebase login --device            only the code (SSH, a VM, no browser)
 nukebase accounts                  list signed-in accounts
 nukebase use you@x.com             default for commands outside a project
 nukebase logout you@x.com          sign out one account
-nukebase logout                    sign out every account
+nukebase logout --all              sign out every account
 ```
 
 Sign-ins are kept in `~/.nukebase/credentials.json`, never inside a project.
@@ -41,9 +41,14 @@ Push and pull carry it, so a fresh clone is already linked.
 ```
 nukebase create <name> [size] [email]   sizes: 128mb, 256mb, 512mb, 1gb
 nukebase link <name> [email]            connect a folder to an existing project
-nukebase push | pull | logs | rollback | backup | restore | env push | domain | ...
+nukebase push | pull | logs | rollback | backups | env push | domain | ...
 ```
 
+Code moves with `push` / `pull`; the app's data (the `backup` paths in
+`package.json`) only with `pull --data` / `push --data`. `rollback` undoes a
+push from the push history kept on the server; `backups` lists the off-site
+backups (every 4 hours, 30 days) and `backups restore <id>` puts one back.
+
 Run `nukebase help` for every command.
 
 ## CI

package/bin/nukebase.js

@@ -48,7 +48,7 @@ Accounts
   login --email-link         sign in with an emailed link instead
   login --password           username + password (the master account)
   logout <email>             sign out one account
-  logout                     sign out every account on this machine
+  logout --all               sign out every account on this machine
   accounts                   list signed-in accounts
   use <email>                default account for commands outside a project
   whoami                     who owns this project, and are you signed in
@@ -62,40 +62,51 @@ New projects
   link <name> [email]        connect this folder to an existing project
 
 In a project folder (runs as the account that owns the project)
+
+ Code
   push                       upload code and restart (--tier <size> if it has
                              to create the project in this region)
-  push --include backup      ALSO upload the backup set, replacing the
-                             server's live data with your copy
   pull                       download code
-  update                     refresh the NukeBase engine files
-  backup [--out <dir>]       download the backup set from the server
-  backup --storage           also the app's files in file storage (new or
-                             changed ones)
-  env push                   make the hosted environment (process.env) equal
-                             to ./.env, then restart the project
-  env list [--show]          variable names set on the server
+  update                     update the NukeBase ENGINE files in this project
+                             (the CLI itself updates with npm i -g nukebase)
+  download [--out f.zip]     the whole project as a ZIP, as the server has it
+
+ Data  (the paths listed under "backup" in package.json)
+  pull --data [--out <dir>]  download the live data to this machine, the
+                             files in file storage too when listed; only new
+                             or changed files, nothing local is deleted
+  push --data                replace the server's live data with your copy
+                             (stops the app first; nothing there is deleted)
+
+ Push history  (one restore point per push, kept on the server)
   rollback [id]              undo a push. Live data is kept.
-  rollback backup [id]       undo a push AND restore the backup set as it was
-                             then; discards writes since
-  rollback list              show restore points (also: restorepoints)
-  restore list               backups in file storage: database and code,
-                             every 4 hours and after each push, 30 days
-                             (also: backups)
-  restore <id>               put one back (--code-only / --data-only);
-                             what it replaces becomes a restore point
-  backup --from <id>         download one: its database into ./server/data,
-                             or everything with --out <dir>
+  rollback [id] --data       also put the data back as it was then; discards
+                             every write since
+  rollback list              show the push history
+
+ Backups  (off-site, every 4 hours, kept 30 days; projects with file storage)
+  backups                    list them
+  backups restore <id>       put one back (--code-only / --data-only); what it
+                             replaces is saved to the push history first
+  backups download <id>      its database into ./server/data, or everything
+                             with --out <dir>
+
+ Running
   pause                      stop the project (base fee + disk still accrue)
-  restart | resume           restart it; also resumes a paused project
+  restart                    restart it; also resumes a paused project
+  logs [--follow]            recent log output; --follow streams
   delete                     delete it on the server; asks for the name
+
+ Settings
+  env push                   make the hosted environment (process.env) equal
+                             to ./.env, then restart the project
+  env list [--show]          variable names set on the server
   domain                     connect a custom domain, step by step
   domain <name> [--email e]  connect in one go (DNS already set)
   domain remove              disconnect the custom domain
   domain email               send the app's emails from the custom domain
                              (--root | --sub, --wait)
   domain email remove        go back to sending from nukebase.com
-  logs [--follow]            recent log output; --follow streams
-  download [--out f.zip]     the project ZIP, exactly as the server has it
   regiontransfer [region]    move this project to another region, step by step
   regiontransfer --to <email>  ... into a different account on the target
 
@@ -105,7 +116,12 @@ Options
   --as <email>               with --region: as another signed-in account
   --yes, -y                  non-interactive (no y/n prompts)
   --no-check                 push even if server-side .js files don't parse
-  --streams <1-8>            parallel connections for big push/pull/backup
+  --streams <1-8>            parallel connections for big push/pull
+
+Older names still work: backup (pull --data), push --include backup
+(push --data), rollback backup <id> (rollback <id> --data), restorepoints
+(rollback list), restore (backups restore), backup --from (backups download),
+resume (restart).
 
 CI: set NUKEBASE_TOKEN and NUKEBASE_UID (create a build token on the
 dashboard under Signed-in devices).