stormforge is the command line client tool to use StormForger from
your command line. It can also be used as a ruby gem for deeper
integration with your tools.
Please note that StormForger is in closed beta right now and you need an account to use it. Visit https://stormforger.com/ to get more information.
stormorge-ruby supports
Add this line to your application's Gemfile:
gem "stormforge-ruby", require: "stormforge"
And then execute:
$ bundle
Or install it yourself as:
$ gem install stormforge-ruby
To get started, run
stormforge auth
This will ask you for your StormForger credentials, aquires your API
token and stores it in ~/.stormforger. Those credentials will be used
for all other requests afterwards.
To set up StormForger for your project, run
stormforge init
This will create a Stormfile with an example test case so you can get
started.
To get more usage information, run
stormforge [SUBCOMMAND] help
This gem will be usable as a library for closer integration to your projects. Right now this isn't officially supported.
git checkout -b my-new-feature)git commit -am 'Add some feature')git push origin my-new-feature)FAQs
Unknown package
We found that stormforge-ruby demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.