If there are no output from the running process on stdout as part of nitric start than the user will see a "No services" messages as part of the CLI output despite the line directly above giving the number of detected entrypoints we have as part of start.
This change provides an initial indicator, that the service began execution without error, we may want to update the message to make it clear that this was from the CLI and not the users application.
In latest version the service name has been replaced with nitric
If there are no output from the running process on stdout as part of nitric start than the user will see a "No services" messages as part of the CLI output despite the line directly above giving the number of detected entrypoints we have as part of start.
This change provides an initial indicator, that the service began execution without error, we may want to update the message to make it clear that this was from the CLI and not the users application.