Tool manifest and microservice getting started#100
Conversation
allister-beamable
left a comment
allister-beamable
left a comment
There was a problem hiding this comment.
Fine to commit as-is, or apply prose wording changes if you like my suggestion.
| dotnet tool install Beamable.Tools | ||
| ``` | ||
|
|
||
| The first three commands create the folder and register a `.config/dotnet-tools.json` manifest. The fourth installs the Beam CLI into that manifest. From this folder, `dotnet beam` runs the locally installed CLI. |
There was a problem hiding this comment.
Something about this prose description feels overly specific; is there a way to phrase it that feels more like warm human segue between code blocks that speak for themselves?
Maybe like, "These commands establish a tool manifest in a new folder of your choice. You can confirm by looking at .config/dotnet-tools.json; when in this folder, dotnet beam will use this specific Beam CLI."
Or something? 😸
Honestly, it reads fine as it is; just spitballing to see if there is room for improvement!
|
We should back-propagate this to |
|
Regarding the question about duplicating |
2 participants
I am not sure about yet if I want to merge this.
On one hand it describes how user can create a tool manifest just like we do during engine integration setup, but on the other it could be a bit of duplicated info which would maybe be better to live in
microservices.md.What do yall think?