Fix::Command

Provides the fix command with several options.

Contact

• Home page: https://github.com/fixrb/fix-command
• Bugs/issues: https://github.com/fixrb/fix-command/issues
• Support: https://stackoverflow.com/questions/tagged/fixrb

Rubies

• MRI
• Rubinius
• JRuby

Installation

Fix::Command is cryptographically signed.

To be sure the gem you install hasn't been tampered with, add my public key (if you haven't already) as a trusted certificate:

$ gem cert --add <(curl -Ls https://raw.github.com/fixrb/fix-command/master/certs/gem-fixrb-public_cert.pem)
$ gem install fix-command -P HighSecurity

The HighSecurity trust profile will verify all gems. All of Fix::Command's dependencies are signed.

Or add this line to your application's Gemfile:

gem 'fix-command'

And then execute:

$ bundle

Usage

First, let's see the API:

$ bundle exec fix --help
Usage: fix <files or directories> [options]

Specific options:
        --debug                      Enable ruby debug
        --warnings                   Enable ruby warnings

Common options:
        --help                       Show this message
        --version                    Show the version

And second, let's run a test:

$ bundle exec fix duck_fix.rb -w
> fix --warnings /Users/bob/code/duck_fix.rb

/Users/bob/code/duck_fix.rb ..I

1. Info: undefined method `sings' for #<Duck:0x007fdbeb05c1d8> (NoMethodError).

Ran 3 tests in 0.000612 seconds
100% compliant - 1 infos, 0 failures, 0 errors

Security

As a basic form of security Fix::Command provides a set of SHA512 checksums for every Gem release. These checksums can be found in the checksum/ directory. Although these checksums do not prevent malicious users from tampering with a built Gem they can be used for basic integrity verification purposes.

The checksum of a file can be checked using the sha512sum command. For example:

$ sha512sum pkg/fix-command-0.1.0.gem
26198b7812a5ac118a5f2a1b63927871b3378efb071b37abb7e1ba87c1aac9f3a6b45eeae87d9dc647b194c15171b13f15e46503a9a1440b1233faf924381ff5  pkg/fix-command-0.1.0.gem

Versioning

Fix::Command follows Semantic Versioning 2.0.

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

License

See LICENSE.md file.