Fleet a side project atPostHog
All packs

Recovery

Threads that stop on a usage limit or a provider outage continue once the provider answers again, and fleet providers says which provider has capacity.

Needs a hub

Add to your Fleet

How it works

  1. A thread hits a usage limit
  2. The hub asks the provider
  3. The provider answers
  4. The thread continues

Workflows

  • Provider recovery

    Off until you turn it onNeeds the Hub pack

    Threads that stop on a usage limit or a provider outage continue by themselves once the provider answers again.

    Read before you turn it on

    Sends continue messages to stopped threads without you in the room, and starts an alert thread in the hub's thread folder.

What it costs

While a thread waits on a limit or an outage, Fleet sends one small request per provider through the hub's proxy, at most every five minutes.

Know before you turn it on

Fleet sends continue messages to stopped threads without you in the room.

Add Recovery to your Fleet

Paste this prompt into a T3 Code thread on a machine that runs Fleet.

Your install prompt

Add this Fleet pack to my setup with me: Recovery.

Fleet already runs on this machine. Ask me each choice with your question tool, and run every command yourself.

1. Run `fleet update`, so this machine has the newest engine and packs. Then run `fleet packs`, and leave out each pack that is already on.
2. This pack needs a hub: Recovery. Run `fleet hub status`. When it prints "The hub: not named", I have no hub yet. Tell me, leave that pack out, and offer to add a hub and a node first with step 9 of https://raw.githubusercontent.com/Silthus/fleet-engine/main/SETUP.md. Otherwise the name after "The hub:" is the SSH name of the hub. Use it as the host of each SSH command in a note.
3. Read the setup note of each pack. Ask me what it asks, and collect the flags that it names. Where a note names "the setup command" or "the command in step 9", use the `fleet packs` command of this prompt. Do not run a step that a note puts after that command yet.
   - Recovery: ~/.local/share/fleet/engine/packs/recovery/SETUP.md
4. Turn the packs on with one command, and add the flags that the notes name:
   fleet packs --add recovery
5. Run `fleet update` on the hub over SSH, so the hub has the packs before a note's next step needs them.
6. Do the steps that each note puts after the command.
7. Run `fleet doctor`, and explain each line. Do each `To do:` line with me, and say what a sign-in is for before it opens.
8. My other machines take the change at their next `fleet update`. To give it to one now, run `fleet update` there.
Open in T3 Code

Add more packs in one prompt