docs: add deployment guides for DigitalOcean, Fly.io, Sprites.dev

[baudbot-agent]

Summary

Add dedicated deployment guides for three cloud platforms in docs/deploy/:

Guides

• docs/deploy/digitalocean.md — DigitalOcean Droplet
• docs/deploy/fly-io.md — Fly.io Machines with persistent volumes
• docs/deploy/sprites.md — Sprites.dev persistent microVMs

What each guide covers

1. Prerequisites (accounts, CLI tools, API keys)
2. Server/Machine creation with actual CLI commands
3. System requirements mapped to platform offerings
4. Baudbot installation (clone → install.sh → configure)
5. Networking and firewall setup (platform-specific + baudbot's built-in iptables)
6. Starting baudbot and verifying it works
7. Monitoring (logs, health checks, platform dashboards)
8. Cost estimates with current pricing
9. Platform-specific tips (backups, scaling, gotchas)

Research

All CLI commands, pricing, and platform details were verified against the actual documentation:

• docs.digitalocean.com — doctl reference, pricing page
• fly.io/docs — Machines, volumes, secrets, pricing
• docs.sprites.dev — CLI reference, working with sprites, billing

[greptile-apps]

Greptile Summary

Added comprehensive deployment guides for three cloud platforms (DigitalOcean, Fly.io, Sprites.dev), each covering prerequisites, system requirements, installation steps, networking configuration, monitoring, cost estimates, and platform-specific tips.

Key additions:

• docs/deploy/digitalocean.md — Droplet-based deployment with doctl CLI examples and cloud firewall setup
• docs/deploy/fly-io.md — Docker-based Machines deployment with persistent volumes and custom entrypoint script
• docs/deploy/sprites.md — Persistent microVM deployment with idle/wake behavior and checkpoint backup support

Issue found:

• docs/deploy/fly-io.md:105 uses incorrect script name (setup.sh instead of install.sh)

Confidence Score: 4/5

• Safe to merge after fixing the script name error in Fly.io guide
• Documentation-only changes with comprehensive, well-researched content. One minor but important error (wrong script name) that would cause the Fly.io deployment to fail
• docs/deploy/fly-io.md needs correction at line 105

Important Files Changed

Filename	Overview
docs/deploy/digitalocean.md	Comprehensive DigitalOcean deployment guide with CLI commands, pricing, and platform-specific tips
docs/deploy/sprites.md	Detailed Sprites.dev deployment guide covering persistent microVMs with idle/wake behavior and checkpoint backups
docs/deploy/fly-io.md	Fly.io deployment guide using Machines and volumes; contains incorrect script reference (setup.sh vs install.sh)

_{Last reviewed commit: 8d78502}

[greptile-apps]

_{3 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

incorrect script name - should be install.sh not setup.sh

Suggested change

	/root/baudbot/setup.sh root
	/root/baudbot/install.sh

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/deploy/fly-io.md
Line: 105

Comment:
incorrect script name - should be `install.sh` not `setup.sh`

```suggestion
  /root/baudbot/install.sh
```

How can I resolve this? If you propose a fix, please make it concise.