Key | Value |
---|---|
FileName | ./usr/share/gems/specifications/apipie-rails-0.3.6.gemspec |
FileSize | 2184 |
MD5 | 1F81C3B075ABF02450E4080F949F08C1 |
SHA-1 | 13EA0BE29FEB0A401B19EA694665F04DD7DC3303 |
SHA-256 | BC1DC66112448FE8144D788BCC8FC22CDA7856D9F8C6543D34C66858D66C2FA8 |
SSDEEP | 24:ZkbcxaO7dsxt1BkG15BUE2wEx5Tp7vzeDuTNzeRZe7eleFeEzI/iQvzwuNzIZ6oK:uBORMTLBUtwEngyxaiSAgEE/tbt/FTd |
TLSH | T1EE41415A05B3E0B133B334C34CDA00A22AF3D1366B86D048B51D69085B18DDF368EBB7 |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 0C8D1624A8F1F12147B6368B89B54156 |
PackageArch | noarch |
PackageDescription | Apipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead of traditional use of #comments, Apipie lets you describe the code, through the code. This brings advantages like: * No need to learn yet another syntax, you already know Ruby, right? * Possibility of reusing the docs for other purposes (such as validation) * Easier to extend and maintain (no string parsing involved) * Possibility of reusing other sources for documentation purposes (such as routes etc.) The documentation is available from within your app (by default under the /apipie path.) In development mode, you can see the changes as you go. It's markup language agnostic, and even provides an API for reusing the documentation data in JSON. |
PackageMaintainer | Fedora Project |
PackageName | rubygem-apipie-rails |
PackageRelease | 1.fc24 |
PackageVersion | 0.3.6 |
SHA-1 | CD56C277B5DA389520FA6AB93450F151F6E296C6 |
SHA-256 | 6332155A3552BA990BDABA0B167C4332CBECA3F2D0573BAB121ACCC79D4C7B05 |
Key | Value |
---|---|
MD5 | 2BF1E91DFC79AD1F82EF49B05DFA9727 |
PackageArch | noarch |
PackageDescription | Apipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead of traditional use of #comments, Apipie lets you describe the code, through the code. This brings advantages like: * No need to learn yet another syntax, you already know Ruby, right? * Possibility of reusing the docs for other purposes (such as validation) * Easier to extend and maintain (no string parsing involved) * Possibility of reusing other sources for documentation purposes (such as routes etc.) The documentation is available from within your app (by default under the /apipie path.) In development mode, you can see the changes as you go. It's markup language agnostic, and even provides an API for reusing the documentation data in JSON. |
PackageMaintainer | Fedora Project |
PackageName | rubygem-apipie-rails |
PackageRelease | 1.fc24 |
PackageVersion | 0.3.6 |
SHA-1 | 22C754944B2C5F55F86581EC1566B26903A0BC58 |
SHA-256 | BBBD265B2F1B3EA639AE9D9F3A4AE8C2C278CD84886371680EC7106943A7F82A |