@stringsync/splates 0.0.54 → 0.0.55

package/README.md

@@ -62,7 +62,7 @@ Keep sensitive information out of them.
 **Heavy jobs.** Hooks (`postCheckout`, `postRewrite`, `preMerge`) run in one
 of the machine's heavy-job slots, two by default (`SPLATES_HEAVY_JOBS` sets
 how many), so several agents testing at once queue rather than run the
-machine out of memory. `splates heavy -- <command>` runs anything else as
+machine out of memory. `splates run -- <command>` runs anything else as
 heavy, such as a test suite an agent runs mid-task, in a slot too.
 
 **Pushing.** With `remote: "origin"` in `splates.config.ts`, each task's
@@ -253,26 +253,9 @@ serving on this machine.
 
 ### Worker providers
 
-To have splates make workers when agents queue for want of a slot, name the
-cloud account to make them in as `splates.config.ts`'s `cloud`, in the repo
-`splates server` starts in:
-
-```ts
-import { AwsCloud } from "@stringsync/splates-server/cloud";
-import type { ConfigFile } from "@stringsync/splates-server/config";
-
-export default { cloud: new AwsCloud() } satisfies ConfigFile;
-```
-
-`AwsCloud` comes with splates, signed with the AWS CLI's sign-in or the
-instance role. Another is a class that implements
-`CloudProvider` from `@stringsync/splates-server/cloud`: making, listing and
-deleting tagged machines, snapshots, SSH keys and firewalls through the
-cloud's API, with its machine types and prices. splates makes both the
-workers and the coordinator's box (`splates server deploy`) over it.
-
-For machines that are not a cloud's, give it a `workerProvider` instead, any
-object that implements `WorkerProvider`:
+To have splates make workers when agents queue for want of a slot, give
+`splates.config.ts` a `workerProvider`, in the repo `splates server` starts in,
+any object that implements `WorkerProvider`:
 
 ```ts
 import type { ConfigFile } from "@stringsync/splates-server/config";
@@ -306,9 +289,9 @@ rate cap, and `splates worker remove` destroys its machine.
 
 The worker budget is in dollars, at each type's list price, so every figure is
 an estimate: a rate cap on what the made workers running at once cost an hour
-($0.25/h by default), and limits on what they cost in a day ($5) and a month
-($75), from the start of each in local time. Past the rate cap no worker is
-made, and the queue says which limit holds it, as `rate cap $0.25/h reached`.
+($1/h by default), and limits on what they cost in a day ($15) and a month
+($200), from the start of each in local time. Past the rate cap no worker is
+made, and the queue says which limit holds it, as `rate cap $1.00/h reached`.
 Once a day's or month's limit is spent, made workers take nothing new, their
 agents are asked to stop at a checkpoint, and each is destroyed once its last
 agent ends. Each limit warns at 80%, 90% and 100%, once in its window, by Web

package/handoff.d.ts

@@ -0,0 +1,13 @@
+/** Set by `checkout.ts` once `splates dev` is mounted on this process. */
+export declare const devMounted: {
+    value: boolean;
+};
+/** The nearest directory at or above `cwd` that is a splates checkout. */
+export declare function checkoutAbove(cwd: string): string | null;
+/**
+ * The release has no `splates dev`, and would print help and exit 0, which
+ * reads as a passing `splates dev test`. Standing in a checkout, run the
+ * checkout's own `bin/splates` instead; anywhere else, fail saying so.
+ * Returns the exit code, or null when `argv` is no `dev` command.
+ */
+export declare function handOffDev(argv: string[], cwd: string): Promise<number | null>;