Replies: 7 comments 5 replies
-
We could build support for experimental features into the core logic of the system, hiding them behind a
The function created would have your example template and custom buildpacks, etc. The structure of that repository would be something like:
The manifest.yaml is optional when providing your own templates, but this is where you would specify the custom buildpack. The other way to use a custom template with custom buildpack is as-needed (no local copy):
|
Beta Was this translation helpful? Give feedback.
-
@aslom Would the project template differ from non-WASM project, or would it be identical (I mean function name package and signature)? |
Beta Was this translation helpful? Give feedback.
-
If the project would be the same and only BPs differ the you might just add mention in the template README.md. |
Beta Was this translation helpful? Give feedback.
-
@matejvasek I think the project would be different as some libraries are not available for Wasm WASI today |
Beta Was this translation helpful? Give feedback.
-
I am going to present today current status: in short I got buildpack to work and generate docker image that I could deploy. Still figuring func repository layout and what is needed to make func create to work |
Beta Was this translation helpful? Give feedback.
-
After learning buildpacks/builder/run/build/images etc. I finally managed to get func create Wasm-WAGI to work - it required rebuilding func with my docker image as trusted builder #1599
|
Beta Was this translation helpful? Give feedback.
-
Instructions and source code: |
Beta Was this translation helpful? Give feedback.
-
Such as Wasm buildpacks that may not be officially supported?
Beta Was this translation helpful? Give feedback.
All reactions