A typical solution may have tens of microservice projects. During development, you usually will have a root folder for the entire solution, with a sub-folder per microservice project inside it.
Unlike traditional model where a large solution can still be a single Visual Studio solution (with multiple projects inside it), in Microservices, each microservice project will be an independant Visual Studio solution, with a separate GIT repository, access permissions, etc. This can make it hard to see the big picture in one view.
This utility will solve that problem, by providing a high level management tool. You can think of it as a complementory tool to Visual Studio.
When first running it, you should point it to the root folder of the solution. It will then go through all sub-folders to determine if it's an Olive microservice. If it is, then it will generate a row on the UI.
Website\Properties\LaunchSettings.json
file.Hub
service, because all other services will be accessible via Hub.In the main menu, you have the Nuget
item with two options:
Under File
menu you have the New Microservice
item. It will open a dialog asking you to input a couple of fields:
When you click Create
it will generate a full Visual Studio solution in the root folder of your project, ready for your development!
BigPicture
Services.json
{
"Solution": {
"ShortName": "geeksms",
"FullName": "Geeks Operating System",
"Nuget": {
"Url": "http://nuget.geeksms.uat.co/nuget",
"ApiKey": "..."
},
"CIServer": {
"Type": "Jenkins",
"Url": "http://jenkins.app.geeks.ltd/"
},
"Production": {
"Domain": "geeks.ltd"
}
},
"Services": {
"Hub": {
"LiveUrl": "https://hub.app.geeks.ltd",
"UatUrl": ""
},
"People": {
"LiveUrl": "https://people.app.geeks.ltd",
"UatUrl": ""
},
...
}