Cool Computers

Save and start the computer's one long-running program and keep it running: after a crash it starts again after 1 s, doubling up to 60 s, and the service counts the restarts. Running it again replaces the service. With port, it is ready once the port accepts connections, and the computer's URL reaches it; without port (a bot or a worker) it is ready once it has stayed up for 5 s, and the URL is unchanged. The result says status running only once it is ready; a program still installing or starting returns status starting with a notice, and keeps starting in the background: check it with cool_get_service, do not run it again. To show something, publish the files with cool_publish (instant, no VM). On a site with no VM it first gives the site its own VM, which cannot be undone: it uses 1 of the account's 20 VMs and memory from its 8 GiB, publishing to it stops, and its files move to /home/runtime/app; once its port is exposed, the service answers every path but a site's functions (/api), and /home/runtime/app is never served as files again, even after the port is removed: the service serves its own static files.

Send one outbound email from an account-owned computer mailbox.

Set the outbound network policy for one account-owned computer.

Make an account-owned computer public or private.

Set the outbound network policy inherited by newly created computers.

Connect a subdomain the user controls, such as app.example.com (no apex, no wildcard; punycode for an internationalized name), to the computer. Give the user the two returned records to create at their DNS provider: the TXT record proves control of the hostname and must resolve within 72 hours, the CNAME sends its traffic to Cool Computers. The same hostname again returns it as it is; another hostname replaces one still waiting for its TXT record. A computer has one domain.

Store a secret set, as cool secrets set does: the keys a site's functions get as env when its cool.json names the set ("secrets": "<set>"), or a VM's programs get with cool secrets exec. It replaces the whole set: send every key it should keep, with its value. Values are stored encrypted and never returned; the result counts the set's keys, and cool_get_secret_metadata lists their names. A Cool Computers API key or access token is refused: store only the keys of the services the code calls. Keys in proxy are sent only to their host: a program gets a stand-in, sends it as the Bearer token in the Authorization header, and the computer's egress proxy puts the real value in its place on https requests to that host. A site's functions get a proxy key only once the site has its VM; before that they get only the plain keys.

Give a person use of a computer by their email address, or take it away: access can_use shares it, none stops sharing it with them. Sharing emails an invitation to someone this account has not shared with yet; state is pending until they accept, active once they can open it. Use it to let someone open a private site. Whoever it is shared with has full use of the computer, its files and the secret set its cool.json names included, and while it is shared it gets no other secret set or integration. The same call again changes nothing and sends no second email. The result lists everyone who can open the computer.

Return one file or folder's type, size, mode and modification time, as cool_list_files sees them, without reading it.

Stop the configured durable service without deleting its configuration or changing HTTP exposure.

Create or reuse a computer and switch it to an authorized GitHub branch workspace.

Remove the selected HTTP route without stopping programs or changing sharing. The URL then shows a page saying the computer serves nothing; a site whose port was exposed never serves its files again.

Check a connected service: test its connection with the service, record its health, and refresh its stored credential when the service asks for that. Reports any action needed to reconnect it. Running it again is safe.

Return the verified account owner for this conversation.

Run SQL against an account-owned site's database. Use sql with optional positional params for one statement, or statements for a transaction. This can change data. A site needs cool.json with database: true and functions, then a published release. Keep SELECT results small with LIMIT.

Write files on a computer with a VM, under /home/runtime, creating their folders; a file that exists is replaced. Files in /home/runtime/app are public at the computer's URL; restart its service with cool_restart_service when it should load them. A site without a VM takes no writes: publish its files with cool_publish, which replaces the whole release, so send every file, unchanged ones included (read them with cool_read_file); omitted files stop being served. Writing never gives a computer a VM.