Service Fabric Explorer is an application for inspecting and managing cloud applications and nodes in a Microsoft Azure Service Fabric cluster.
Windows | Linux / macOS |
---|---|
For more information about the application and how to use it: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-visualizing-your-cluster
To develop Service Fabric Explorer, the following components are required.
- Git: https://git-scm.com/
- Node.js (use LTS version): https://nodejs.org/
The recommended IDE for Service Fabric Explorer development is VSCode because VSCode is a cross-platform editor, which supports Windows, Linux and macOS. But you can use whatever editor to develop.
Here's a list of common IDE used.
- VSCode: https://code.visualstudio.com/
- Visual Studio: https://www.visualstudio.com/
-
Clone the master branch.
git clone --recurse-submodules https://github.com/Microsoft/service-fabric-explorer.git <path to the local folder>
-
Install project dependencies: This can be done inside VSCode or use a console window.
- [SFX] install the following CLI for the angular project
npm install -g @angular/cli
- [SFX] Navigate to
src/SfxWeb
and run the following scripts.
npm install
- [SFX Proxy] Navigate to
src/Sfx-Proxy
and run the following scripts.
npm install
-
Build projects
- VSCode
- Open
src/SfxWeb
andsrc/Sfx-Proxy
in VSCode with multiple-root workspce.
- Open
- Console
- [SFX] Navigate to
src/SfxWeb
and run the following scripts. For a develop/quick build
For a production buildnpm run build
npm run build:prod
- [SFX] Navigate to
- VSCode
Navigate to src/SfxWeb
npm start
Navigate to src/Sfx-Proxy
npm start
There are 2 optional flags -r which would record every request to a folder(by default called playbackRecordings) and overwriting if the same request is made again -p every request will be checked for a saved response and if one exists get served instead
npm start -- r p
If proxying requests to a secure cluster adding a file called localsettings.json to src/Sfx-Proxy can take a cert pfx location like below.
{
"TargetCluster": {
"Url": "https://test.eastus.cloudapp.azure.com:19080",
"PFXLocation": "C:/some_cert.pfx",
"PFXPassPhrase": "password"
},
"recordFileBase": "playbackRecordings/"
}
Navigate to src/SfxWeb
folder and run
npm test
Navigate to src/SfxWeb folder and run
npm run cypress:local
This assumes that the angular local dev server is running
(see the following for reference https://lukas-klement.medium.com/implementing-code-coverage-with-angular-and-cypress-6ed08ed7e617)
Run a full E2E suite above and this will generate a code coverage report. Navigate to src/SfxWeb folder and run
npm run test:coverage
Then you can also view a full report at
sfxWeb/coverage/lcov-report/index.html
The CI will run the following
- production build
- unit tests
- E2E tests
For questions related to Azure Service Fabric clusters, take a look at the tag on StackOverflow and official documentation.
If your issue is not specific to the Service Fabric Explorer, please use the Service Fabric issues repository to report an issue.
If your issue is relevant to the Service Fabric Explorer, please use this repositories issue tracker.
Be sure to search for similar previously reported issues prior to creating a new one. In addition, here are some good practices to follow when reporting issues:
- Add a
+1
reaction to existing issues that are affecting you - Include detailed output or screenshots when reporting unexpected error messages
- Include the version of SFX installed
- Include the version of Service Fabric runtime for the cluster you have selected
We encourage everyone to contribute to this project, following the contribution guidelines below. If you have ideas and want to share these with the community before taking on implementing the change, feel free to suggest these using issues.
For general contribution guidelines, plese see here: https://github.com/Microsoft/service-fabric/blob/master/CONTRIBUTING.md