-
Notifications
You must be signed in to change notification settings - Fork 33
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
feat: Adds flake #517
feat: Adds flake #517
Conversation
Adds a nix flake for usage in building things. It is still missing the ability to run an e2e test and build docker images, but it does work for both building and nix shell Signed-off-by: Taylor Thomas <[email protected]>
Signed-off-by: Taylor Thomas <[email protected]>
Signed-off-by: Roman Volosatovs <[email protected]>
Special thanks to @rvolosatovs for helping me figure out the cargo.toml munging |
6181570
to
772971a
Compare
serde_json::to_vec(&DeleteModelRequest { | ||
version: None, | ||
}).unwrap(), | ||
serde_json::to_vec(&DeleteModelRequest { version: None }).unwrap(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: These changes were just a missing cargo fmt
that I found while running tests in the flake
772971a
to
be21e2b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good to me, only a supernit and a question. Is it worth throwing a comment at the top of the flake marking it as experimental? Only to consider whether or not we're going to update & maintain it often
Signed-off-by: Taylor Thomas <[email protected]>
be21e2b
to
e434442
Compare
This adds a
flake.nix
and associated files for a dev environment via nix and steps for building all the parts of wadm in an incremental way. Part of this was an experiment to see what we could get nix to do with monorepo deps in the simple case. Please note that this does not actually add this as part of the build pipeline, just adds the file the repo for people to use. Maybe in the future we can add in builds and caching into our pipelines.