Deploying To Remote Clouds

When to use

• Target is a real Taubyte cloud (not Dream local)
• Switching from Dream to remote (or vice versa)
• After a tau push project to remote, build status is unclear
• Error: project ids not equal <patrick> != <yaml>
• Generated domain looks wrong (or you're about to create one and aren't sure if you're on remote)
• Verifying that GitHub webhook delivery actually reached the cloud

Mental model

A remote Taubyte cloud is reached by FQDN rather than by Dream universe. After git push (or tau push project), the cloud is notified by a GitHub webhook, builds happen automatically, and serving picks up the latest successful build. There is no dream inject step for remote — that's Dream-only. Verification therefore relies on tau query builds/build/logs and, when those are silent, GitHub's webhook delivery records.

Selecting a remote cloud