~ knotless Search/
↑↓ move↵ open⇧↵ all results

socialweb.computer/socialweb-computer-kcp

socialweb.computer: a compute market on atproto (kcp)

1 collaborator
0
0
40 lines · 1.6 KB Raw History

One gateway in front of the whole market

You don't have to run your own requester, watch the relays, or pick bids. The gateway at k8s.socialweb.computer speaks XRPC on one side and the decentralized market on the other: ask for a Kubernetes cluster, and it requests the cluster's nodes on the market for you, as VMs, with the same RFP, bid, accept and receipt records.

In a browser

Sign in at k8s.socialweb.computer, create a cluster, pick a lifetime (1, 8 or 24 hours, or no expiry), download its kubeconfig, revoke it.

From the CLI

One call per step, given a goat account login session of your account and a service-auth token per call. The commands, from creating a cluster to deleting it: gateway.md.

GW=https://k8s.socialweb.computer AUD=did:web:k8s.socialweb.computer N=com.publicdomainrelay.temp.cluster
goat xrpc procedure "$GW" "$N.createCluster" name=my-cluster \
  "Authorization:Bearer $(goat account service-auth --aud "$AUD" --lxm "$N.createCluster")"

Your own gateway

The same gateway runs in your own requester, with no web app: run requester --with-gateway; and in a local market: dev up --with-gateway (quickstart-local.md).

Rather request one VM?

The gateway is for clusters. One VM is one command from your own terminal:

<!-- ../../README.md#request-a-vm -->

Prefer to run it yourself?

Every record the gateway writes is one you could write yourself: see the raw protocol.