Managing apps in the Eagle 3D Streaming Control Panel: stream links, new versions, choosing which version runs, rolling back, and deleting things you no longer need.
A stream link is the URL you share. Generate one from your app in the Control Panel, then attach a configuration to it — the settings belong to the link, not to the app, so one app can have several links behaving differently.
Use the update icon on the app, then upload the new ZIP. What happens next depends on a setting you chose earlier:
| Version control | Result |
|---|---|
| On | A new version is added. The old one stays and can be selected. |
| Off | The new build replaces the old one, which is gone. |
With version control on, you can select which version runs, and delete versions you no longer want. That combination is what makes an update reversible.
When a new build turns out to be broken, there are two ways back and they are not equally safe.
Get the old build — from the old Control Panel, or from your own S3 storage on Enterprise — and upload it as a new version. Slower, and it is a normal deployment with nothing unusual to go wrong.
Delete the broken version on the VM and rename the previous one in its place — delete v10, rename v9 to v10. Fast, and entirely manual.
Both routes assume you still have the previous build. With version control off, uploads overwrite — so turn it on before you need it, not after.
Deleting removes the application and its versions. Its stream links stop working. This is not reversible, and re-uploading produces a new application rather than restoring the old one — so any links you had shared stay dead.
The six phases an upload passes through, and what a stall in each one means.
Last updated