feat: Implement basic Module Build Server #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsantell
reviewed
May 21, 2024
| pub struct JavaScriptBaker {} | ||
|
|
||
| #[async_trait] | ||
| impl Bake for JavaScriptBaker { |
rust/usuba/Dockerfile
Outdated
|
|
||
| WORKDIR /usuba | ||
|
|
||
| EXPOSE 8888 |
…mponents/service-worker feat: On-demand Isolated Modules SW polyfill
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change proposes a minimum viable implementation of the Build Server described in On-demand Isolated Components.
The implementation is written primarily in Rust, and currently supports building Modules of one language type: JavaScript. It depends on
@bytecodealliance/jco(an NPM package) to be available in its environment.Currently, the server persists built Modules to a temporary database that is deleted as the process stops and cleans up.
There has been an attempt to correctly document the REST API using an OpenAPI spec. When running the server, the API spec is available at http://localhost:8080/openapi.json. Additionally, Swagger UI (a GUI for exploring an OpenAPI spec) is available at http://localhost:8080/swagger-ui. Theoretically, this will allow us to automatically generate REST API clients for the build server in most languages.