|Number of watchers on Github||21|
|Number of open issues||0|
|Average time to close an issue||4 months|
|Average time to merge a PR||about 1 hour|
|Open pull requests||0+|
|Closed pull requests||2+|
|Last commit||over 2 years ago|
|Repo Created||over 4 years ago|
|Repo Last Updated||over 2 years ago|
|Organization / Author||fsstorm|
|Do you use FsStorm? Leave a review!|
|View FsStorm activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
A project for defining and running Apache Storm topologies in F#
Update: Insights gained from working with FsStorm have led to a spinoff: FsShelter, check it out if you like the idea of statically typed topologies.
Building from command line runs the unit tests. IDE: Install NUnit plugin for VS or MonoDevelop to see the unit-tests in Test Explorer and step through the code under debugger.
Have a local Storm installed and running. Make sure F# interpreter is in the path and from the repository root run:
or, if running on Mono:
Open Storm UI and see the Storm worker logs for runtime details.
When running on Mono, it can sometimes be useful to pass additional command line arguments to mono when launching a component. For example, you may want to run a profiler:
mono --log:report program.exe
In order to accomplish this with FsStorm, you will need to do the following:
Config = jval [ Storm.Config.useShellScript, jval true ]in your topology definition for the desired component.
.shextension in your project that matches the
Idof the desired component. For example,
AddOneBolt.sh. The content of the script should invoke mono with the desired arguments and specify the name of your executable:
sh #!/bin/bash mono --profile=log:report FstSample.exe