Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Apihistogram Laravel Package

arnulfosolis/apihistogram

View on GitHub
Deep Wiki
Context7

ApiHistogram

ApiHistogram aims to create a history of your API responses and stores the response in your database, so you can analyse variable data coming from any web service that does not offer historical data, or to create your own historical data based on a third party service.


Installation

  • First add ApiHistogram to your project with composer.
    • Composer: composer require arnulfosolis/apihistogram @dev
  • Then, if needed, call composer install or composer update to get all the dependencies set.
  • Make sure that the ApiHistogramBundle is registered in the AppKernel.
    • All ApiHistogram Classes lay under:
      • Namespace: ApiHistogram\.
  • Fill the needed configuration in the your target's config.yml file.
    • See README_CONFIG.md file under /ApiHistogram directory
  • Make sure you set your database's configuration in the parameter's file.
  • You're done!

Description

ApiHistogram allows developers to query API data and save the response data automatically while trying to be the most flexible as possible. ApiHistogram focuses on performance, so all calls are asynchronous.

This allows to have "LIVE" data coming every time the command line tool is called php app/console api-histogram:update


Usage

  • To use the application, make sure you define your sitesin the configuration file config.yml.
    • Recommendation: Use a separate file to define your calls.
  • And every time you call the command php app/console api-histogram:update ApiHistogram will append the new data to the database.

Future development

  • The Api calls are now being used with a simple GET HTTP method. As this is a good approach for a REST-full approach, no extra headers are being placed in the request. So next step will be to add optional headers to the HTTP Request.
  • For now, all data is being saved in one schema in one connection, in future releases using different schemas for different connections for individual calls will be possible.
  • New ideas coming soon!

Contact

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
comsave/common
alecsammon/php-raml-parser
chrome-php/wrench
lendable/composer-license-checker
typhoon/reflection
mesilov/moneyphp-percentage
mike42/gfx-php
bookdown/themes
aura/view
aura/html
aura/cli
povils/phpmnd
nayjest/manipulator
omnipay/tests
psr-mock/http-message-implementation
psr-mock/http-factory-implementation
psr-mock/http-client-implementation
voku/email-check
voku/urlify
rtheunissen/guzzle-log-middleware