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
omnix-cli will be a "super CLI" for Nix of some sort. Where possible, we will expose the functionality as Rust libraries (which can be used by other clients, like omnix-gui).
To begin with, we will have omnix-cli to do two things:
Initialize flakes
om init
This should support a registry of flake templates (use our various flake-parts modules), initialize them using nix flake init as well as fill in any user-specific content using the templateGenerators idea in flake-parts/templates#7 (comment)
The goal is to have om init create flakes for any kind of stack, eventually.
On a flakified project, display a "dynamic README" of some sort that tells any product-oriented person as to how to interact with it. Eg. build the project or run it. If there are services, tell how to run these services. The 'metadata' for this should be standardized somehow. At a basic level, meta.description can be used to describe derivations (including devShells); how do we want to describe, for example, services?
omnix-cli
will be a "super CLI" for Nix of some sort. Where possible, we will expose the functionality as Rust libraries (which can be used by other clients, likeomnix-gui
).To begin with, we will have
omnix-cli
to do two things:Initialize flakes
This should support a registry of flake templates (use our various
flake-parts
modules), initialize them usingnix flake init
as well as fill in any user-specific content using thetemplateGenerators
idea in flake-parts/templates#7 (comment)The goal is to have
om init
create flakes for any kind of stack, eventually.See #152
Inspect flakes
Warning
To be fleshed out.
On a flakified project, display a "dynamic README" of some sort that tells any product-oriented person as to how to interact with it. Eg. build the project or run it. If there are services, tell how to run these services. The 'metadata' for this should be standardized somehow. At a basic level,
meta.description
can be used to describe derivations (including devShells); how do we want to describe, for example, services?Note
om show
should also show a status indicator forom health
(which runs https://github.com/juspay/nix-health)Progress
omnix
#138omnix-cli
crate #144omnix
library crate #146omnix-cli
: Initialize CLI argument handling #148om show
#147om init
- for smart template generation #152om health
(Health checks) #150om ci
#179omnix-cli
: Add autocompletion #56omnix-cli
#149om ci
#151The text was updated successfully, but these errors were encountered: