- How do I install Mining Manager in a Laravel application?
- Install it with Composer using composer require mattfalahe/mining-manager, then rely on Laravel package auto-discovery or register the service provider manually if your Laravel version requires it. Publish and review the package configuration, run any provided migrations if it persists statistics, and define your pools, rigs, and workers in config. Schedule the package's Artisan synchronisation command in app/Console/Kernel.php or the Laravel 11+ scheduler so telemetry is polled regularly. Confirm the supported Laravel and PHP versions in the package composer.json before installing.
- Which Laravel versions does Mining Manager support?
- The provided overview does not list explicit Laravel or PHP version constraints, so check the package composer.json and README for the authoritative requirements. If you deploy it as the SeAT plugin described in the technical evaluation, the effective Laravel and PHP versions are constrained by your SeAT release rather than by the package alone. Pin both the package and your Laravel or SeAT version in composer.json and test upgrades in staging. Do not assume compatibility with the newest Laravel release without verifying.
- What mining metrics can I track with this Laravel package?
- The package is positioned around per-rig hashrate, temperature, and fan-speed monitoring, with pool and worker configuration management. It also advertises share and profitability statistics, so dashboards can show output and earnings alongside hardware health. Uptime and degraded-miner signals are intended to be surfaced through event hooks. Exact metric coverage depends on what your pool APIs and hardware expose, so validate field availability before building reports.
- How does scheduled synchronisation work in Mining Manager?
- Polling is handled by Artisan commands that you register with Laravel's scheduler, which fits naturally into an existing application's cron-driven workflow. Those commands collect pool and rig statistics and persist them for later reporting. For production, run synchronisation on dedicated queue workers and make scheduler ownership explicit, especially if the package runs inside a shared SeAT deployment. Watch external API rate limits and add backoff or jitter so scheduled polls do not overlap.
- Can I receive alerts when a rig overheats or a miner goes offline?
- Yes, the package advertises event hooks intended for alerts on failing hardware, so you can attach Laravel listeners to send notifications when hashrate drops, temperatures rise, or a worker goes offline. Keep alert thresholds in configuration rather than hard-coding them, and route notifications through your existing mail, Slack, or webhook channels. If you use the SeAT plugin release, note that webhook alert toggles can remain silently disabled after upgrade, so verify alert delivery after every deployment.
- Is Mining Manager a standalone Laravel package or a SeAT plugin?
- The package overview presents it as a configuration-driven Laravel package, but the technical evaluation concludes the release functions as a SeAT plugin rather than a generic Laravel module. That distinction matters: a SeAT plugin extends SeAT's Eloquent models, permissions, scheduler, and ESI integration, and it assumes SeAT is your system of record. Confirm which mode you are adopting before installation, because a SeAT plugin should be pinned to a compatible SeAT instance and isolated behind an internal adapter rather than leaked into core domain code.
- What credentials, ESI scopes, or corporation roles does it require?
- The evaluation notes that the reviewed release adds no new ESI scopes, but it still depends on SeAT's existing corporation and character integration plus wallet access for financial workflows. You should confirm exactly which ESI scopes and director-level roles are needed before granting access, and apply least-privilege SeAT roles. Avoid storing pool or miner credentials in the application unless the package explicitly supports secure storage. Restrict wallet, payment, refund, and export features to trusted roles.
- How should I handle payments, balances, and refunds if I use this package?
- Treat the financial side as money-adjacent ledger state, not simple telemetry, and build reconciliation and audit controls around payment matching, remainder cascades, account balances, and refunds. Define a clear source of truth for balances, surface discrepancies against the corporation wallet, and review manual Mark as sent flows carefully. Restrict director-level financial features through SeAT permissions. Invoice immutability after issue is a useful control, but it does not replace periodic reconciliation.
- Is Mining Manager production-ready and actively maintained?
- Adoption signals are weak: the evaluation cites roughly three stars, zero dependents, and an apparent single maintainer, which implies bus-factor and validation risk. It is best treated as a proof-of-concept or reference accelerator rather than an unexamined core dependency. Verify tests, CI, a security policy, and the release and upgrade policy before relying on it. If you proceed, isolate it behind an adapter and plan a rollback path.
- What license does Mining Manager use, and what are the alternatives?
- The evaluation flags GPL licensing as a material risk for distributed or customer-facing products, so legal review is required before embedding or exposing it. Alternatives include writing a small Laravel integration against pool APIs with the HTTP client, scheduler, and events, or using SeAT-native modules if SeAT is already your system of record. A custom adapter gives you clearer control over licensing, data models, and upgrade policy, at the cost of building the polling and persistence layer yourself.