Serving
How does the local-to-cloud loop work?
The local-to-cloud loop runs the same schema on a laptop catalog and on a hosted database, so you change it locally and then apply it remotely.
Updated
How it works
- Apply the file to a local directory.
- On a hosted database, update the runtime first, then the schema, then the service, all against a pxt:// target.
- Applying the schema before the runtime fails with 404: UDF not found.
What it is not
It is not rewriting the application against a different cloud API.
local-to-cloud loop: this, and the thing it is confused with
| This | Not this | |
|---|---|---|
| Schema | One file | Two codebases |
| First target | Local catalog | A cloud project |
| Later target | Hosted database | A translation layer |
Where Pixeltable fits
Pixeltable’s hosted order is pxt db update, then pxt schema update, then pxt service update against pxt://. Locally, pxt schema update applies the same file to a directory.
Questions
- How does local-to-cloud loop work?
- Apply the file to a local directory. On a hosted database, update the runtime first, then the schema, then the service, all against a pxt:// target. Applying the schema before the runtime fails with 404: UDF not found.
- What is local-to-cloud loop often confused with?
- It is not rewriting the application against a different cloud API.