Key | Value |
---|---|
FileName | ./usr/share/gems/specifications/apipie-rails-0.5.5.gemspec |
FileSize | 1873 |
MD5 | 6FD39B9EAF08D3125D9B8975A42E1BE7 |
SHA-1 | 1EB2B0F295CEDF62781FBC8BEAE5804E9DE16C9D |
SHA-256 | F597FA6940E7A0F3BC24A189B7D7A975B2E37C40582A270D9D7725FD5AE6068B |
SSDEEP | 24:ZkbBLmen5LVtAIn6F1GLSnBUE2jAUMpRL1TN0mcmsmSmymE3kQ/x9N0rDFNr3kqA:uIenXitFvBUtdqL1xFdtvPEv/xrI8 |
TLSH | T1FD31EA1E4DB3706176732BC3C8D600A216BBD4151B8EDD88B6095D2C191BF87775A673 |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | E341B4E1AFF93060D52FFF3425DB976E |
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 | 8.fc33 |
PackageVersion | 0.5.5 |
SHA-1 | 3D290D15D65E331D3A5CEAE44906420320329C95 |
SHA-256 | 0790B493CC629E46BDC5990AF99F0AF5A5AD4C5C80C8479FBBD7F059554D6B53 |