Result for 1823870724F65E33DAE105B728267744A0152A34

Query result

Key Value
FileName./usr/share/gems/gems/apipie-rails-0.3.4/app/controllers/apipie/apipies_controller.rb
FileSize4376
MD5E22CF23FE3CE8E8FE193629D68B850FD
SHA-11823870724F65E33DAE105B728267744A0152A34
SHA-256D222A84051AB16CA660B13D60F7776A03EC41B82D84C83E840EE949615CA761C
SSDEEP96:ubegJewDhZId1a4e6ZI14m/QLlCGe2iB4lClJTlZ9AkQn:We2DhCeX/3QLDe2iB4sTlnAkQn
TLSHT1B691618B4865887671C5C7DA98D02E522F2611233F842A28BC0E17855FAAF90E2F7BD4
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

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
MD5BCCCB981FB260ABCFA6DD8BC31BD8683
PackageArchnoarch
PackageDescriptionApipie-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.
PackageMaintainerFedora Project
PackageNamerubygem-apipie-rails
PackageRelease1.fc23
PackageVersion0.3.4
SHA-1076DA0B2EDC9D98DBB41E8DE4198E4D25E53F9CA
SHA-25682CDF357DE84C9C8BD5C743C1E6CE76142145D4CCD4C1AC300E8862AEE281BA6
Key Value
MD5BF4DC975435C624879A13A98391F5C84
PackageArchnoarch
PackageDescriptionApipie-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.
PackageMaintainerFedora Project
PackageNamerubygem-apipie-rails
PackageRelease1.fc23
PackageVersion0.3.4
SHA-15447376863400AFBE82BA0BF1837A880A06E82B4
SHA-25688A70464A02EB9562BA4D53D45309D0485AD7D821CA5BE72B207CCCDB280A931
Key Value
MD52AE33C78267FB39A819B91C97ABDC64D
PackageArchnoarch
PackageDescriptionApipie-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.
PackageMaintainerFedora Project
PackageNamerubygem-apipie-rails
PackageRelease1.fc23
PackageVersion0.3.4
SHA-165245C9570411CCDEADB16A893CEF6BF80EEA974
SHA-2563E44B962736D4EC3CE9EE93A016728BC75CB2FFF7C8C4B3472EE1DF876456373