Registering Dream Repositories

When to use

• A website or library was just imported (tau import website|library), and dream inject push-specific for that repo isn't producing a build.
• The project was bootstrapped with dream inject push-all but website/library builds are still silent.
• The local cloud doesn't seem to know about a repo even though websites/<name>.yaml / libraries/<name>.yaml references it.
• Mirroring what the Console does when wiring a GitHub repo to a local Taubyte cloud.

Why this is needed

A remote cloud receives GitHub webhooks automatically. On Dream, the local auth/repository service has to be told about each website/library repo before it will accept hook-style pushes for it. tau import website|library clones the repo locally but does not always register it with the local service.

Workflow