Key | Value |
---|---|
FileName | ./usr/share/gems/gems/apipie-rails-0.3.4/app/views/apipie/apipies/resource.html.erb |
FileSize | 2219 |
MD5 | 1A517AA698C4BECB2FFFA5275FD3BDF0 |
SHA-1 | 1FA2D086A59BB6115708FE625882373617387BD1 |
SHA-256 | 36B1267B2779D3E5554AC2BB7F4591AEA311A3D2854A3DBFE217D8F5D8570248 |
SSDEEP | 24:G48E0laaMgFOV4LJMYiSGq+K4T5N2193+vl9c/xV8XipPeMNuf6wZOnkNBf2FiLm:miB3YD+Zhvl+/xV8XiIv6olGLx5Ln7 |
TLSH | T17941DF675CF4023262AAD13DF9A82F1B9922A743D566980CB5ED553B9FF4BE0C473180 |
hashlookup:parent-total | 3 |
hashlookup:trust | 65 |
The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | BCCCB981FB260ABCFA6DD8BC31BD8683 |
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.fc23 |
PackageVersion | 0.3.4 |
SHA-1 | 076DA0B2EDC9D98DBB41E8DE4198E4D25E53F9CA |
SHA-256 | 82CDF357DE84C9C8BD5C743C1E6CE76142145D4CCD4C1AC300E8862AEE281BA6 |
Key | Value |
---|---|
MD5 | BF4DC975435C624879A13A98391F5C84 |
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.fc23 |
PackageVersion | 0.3.4 |
SHA-1 | 5447376863400AFBE82BA0BF1837A880A06E82B4 |
SHA-256 | 88A70464A02EB9562BA4D53D45309D0485AD7D821CA5BE72B207CCCDB280A931 |
Key | Value |
---|---|
MD5 | 2AE33C78267FB39A819B91C97ABDC64D |
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.fc23 |
PackageVersion | 0.3.4 |
SHA-1 | 65245C9570411CCDEADB16A893CEF6BF80EEA974 |
SHA-256 | 3E44B962736D4EC3CE9EE93A016728BC75CB2FFF7C8C4B3472EE1DF876456373 |