chore: Specify API host for runtime, deriving other addresses as needed #1818
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when the runtime connects to an incorrect/invalid server (e.g. forgetting to run local server), the web socket connection retries until success, leaving the runtime initialization hanging. A general "API host" URL is needed for the runtime in order to ping the status, which would circumvent this socket loop scenario and alert that the
server is invalid. A simple health ping check has been added.
With an API host URL, other runtime values can be derived, removing redundant params.
With static asset cache no longer explicit, and all but runtime usage of StaticCache being in a Deno environment, the StaticCache functionality now explicitly uses HTTP or the filesystem (StaticCacheHTTP and
StaticCacheFS).
Summary by cubic
Switch Runtime to a single apiUrl host and derive storage and static addresses internally. Shell now performs a runtime health check to catch wrong-backend connections early.
Refactors
Migration