-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for including additional crates #2
Comments
As per zulip conversation with @pepoviola |
Had a look at https://github.com/LukeMathWalker/cargo-chef. It could be useful for managing the building of multiple base images if we need to go to workspaces but not a requirement at the moment. |
Now that we have a couple of templates this might be worth some further consideration.
Another route could be
It's also worth noting that other FaaS solutions just bundle all the options in and pass it to you as a context object and ignore extensiblity somewhat we could take that approach by having an Uber_State object. |
Currently the base image only includes serde to handle JSON messages and surf for http requests.
It's unclear at the moment if the best way to handle the inclusion of additional crates to the base image is to add the ability to reference other base images or pickup a Cargo.toml from the same directory as the functions.rs.
Allowing multiple base images is probably less work in roche but adds complexity for endusers as they have to understand the baseimage construct.
Using a Cargo.toml could possibly add to the build time significantly which would defeat the purpose of this tool.
The text was updated successfully, but these errors were encountered: