bstrie
bstrie
cc https://github.com/enarx/enarx/pull/1862 .
For 0.5, our goal is to support the following initial set of languages: * Javascript * Rust * Go * C * C++ * Python
Rather than `enarx new`, I'd go with `enarx init` to follow the example of `git init` and `cargo init`.
These days we have `enarx config init` for initializing a basic Enarx.toml. Adding additional commands to edit, or initialize from a template, or initialize interactively, may still be desired.
@abhinandanudupa I haven't looked into it at all, so I have no preferences. What I would like is for all of our repos to use the same tool for this,...
TODO: define slug, including `@#` syntax.
For allowing third-party applications to extend Enarx, I agree that this makes sense. However, regarding moving current Enarx functionality into plugins, what would the objective be? Is it to let...
I'm also concerned about what this would mean for `enarx help` output. If we start shipping, say, `enarx repo` as a plugin, then will it show up in `enarx help`?...
Regarding 3, see https://github.com/enarx/enarx/issues/1958 .
Marking this as a draft for now so that it doesn't get merged, since we can't release with a git dependency.