- How do I install the MetaFive Laravel MetaTrader 5 client?
- Install it with Composer using aleedhillon/meta-five, publish the package config, and set the MT5 gateway URL, port, and manager credentials through environment variables or a secrets manager. Confirm the package's Laravel and PHP version bounds in composer.json before planning the integration. A happy-path connection should take days rather than weeks, but the real effort is standing up and licensing the MT5 Web API gateway outside this repository.
- What Laravel and PHP versions does aleedhillon/meta-five support?
- The expected envelope is Laravel 9, 10, or 11 with PHP 8.1 or newer, but you should verify the exact constraints in composer.json and any CI configuration. The package has a single 2024-05 release, so test it against your pinned Laravel and PHP versions before committing. Do not assume broad version support without checking the repository.
- Does this package stream real-time MT5 quotes or tick data?
- No. MetaFive is a thin outbound HTTP adapter over the MetaTrader 5 Web API, not a streaming client or trading engine. Real-time quotes, sub-second execution, and tick streaming are out of scope and would require a different transport such as native MT5 gateway sockets or a broker-side feed.
- How does MetaFive handle MT5 Web API authentication and session token expiry?
- The MT5 Web API auth model is stateful: an authentication handshake returns a session token with a bounded lifetime, so refresh logic is required. Confirm in the package code whether it manages re-authentication or expects the caller to handle token expiry. If it does not, build refresh and retry behavior into your internal client layer.
- Can I call the MetaFive facade directly from Laravel controllers?
- It is better to place the package behind an internal Mt5Client interface rather than calling the facade directly from controllers or Livewire and Inertia components. Trading calls need idempotency, reconciliation, and audit logging that this package does not provide. An interface also keeps the package swappable and caps vendor risk.
- What MT5 Web API endpoints does aleedhillon/meta-five cover?
- Coverage is unverified from the outside, so assume it wraps a useful subset such as auth, users, symbols and quotes, orders and positions, and history. Audit the package endpoint by endpoint against your required call list before committing. With 35 stars and a single release, do not assume complete API coverage.
- Is aleedhillon/meta-five production-ready and actively maintained?
- Treat it as a convenience wrapper rather than a strategic dependency: bus factor is one, community presence is minimal, and there is no visible commercial backing or SLA. Confirm the maintainer is reachable for security fixes and define a fork-and-own trigger before production use. Exit cost is low to moderate, estimated at one to two engineer-weeks for an internal fork or a raw Guzzle client.
- Does MetaFive handle retries, errors, and MT5 retcode mapping?
- The package is a thin Guzzle transport, so do not assume it provides a full retry policy, token refresh, or retcode-to-exception mapping. Verify the actual behavior in code before relying on it. These concerns belong in your internal Mt5Client implementation, where you can enforce idempotency and audit logging.
- How should I test a Laravel app that uses the MetaFive MT5 client?
- Test coverage for the package is unknown, so put your own contract tests around the internal Mt5Client interface and mock Guzzle HTTP responses. Avoid hitting a production MT5 gateway from automated tests, and use test credentials stored outside committed .env files. If possible, validate against a staging gateway before release.
- What are alternatives to aleedhillon/meta-five for Laravel MT5 integration?
- You can implement a raw Guzzle client against the MT5 Web API or fork this package behind the same internal Mt5Client interface. If you need real-time quotes or tick streaming, use native MT5 gateway sockets or a broker-side feed instead of the Web API wrapper. The same interface-first approach applies even in greenfield projects.