You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
As described in the wiki, we are going to split our configuration file into two parts: build time and deployment time. Currently we have a single configuration file that is bundled in the Wasm binary itself, though an OCI-based package format has been proposed for similar purposes:
I tried the proposed tooling on those blogs. It cannot be simply compared with the current bundling format (on disk), because the OCI format rather defines a way to resolve contents on the registry. However, as it allows the data to be addressed by content, it could be beneficial if keepmgr provides caching and the same Wasm files are reused with different configurations.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As described in the wiki, we are going to split our configuration file into two parts: build time and deployment time. Currently we have a single configuration file that is bundled in the Wasm binary itself, though an OCI-based package format has been proposed for similar purposes:
This issue is to check whether the OCI package format meets our needs. #22 probably depends on this.
The text was updated successfully, but these errors were encountered: