Weave Code
Eseye Laravel Package
eveseat/eseye
ESI Eye is a Laravel client for EVE Online's ESI API, built for SeAT. It offers a fluent, expressive interface that handles authentication, token refresh, caching, and error handling, making it easy to query characters, corporations, alliances, and more from your application.
A Standalone PHP ESI (EVE Swagger Interface) Client Library
Frequently asked questions about Eseye
- How do I install eveseat/eseye in a Laravel SeAT application?
- Install it with Composer by requiring eveseat/eseye, then let Laravel package auto-discovery register the service provider and facade. Publish the package config with the vendor:publish command and run any migrations the package ships with. After that, open the SeAT settings screen to enter your EVE Eye credentials and enable the scheduled sync. Check the composer.json constraints against your PHP and Laravel versions before requiring it.
- Do I need SeAT to use eveseat/eseye, or does it work in a standalone Laravel app?
- SeAT is a hard dependency in practice: the package stores tokens through SeAT's user model, reads SeAT roles and squads, and registers its settings inside the SeAT UI. It can run in a SeAT-compatible Laravel application, but it is not a generic drop-in ESI client for any Laravel project. If you are not on SeAT, wrap your own ESI client behind an interface instead of forcing this one to fit.
- Which Laravel, PHP, and SeAT versions does eveseat/eseye support?
- Check the illuminate and php constraints in the tagged composer.json before installing; the package is aimed at the Laravel 9 to 11 era with PHP 8.1+ and SeAT 4/5-style plugin surfaces. Because SeAT itself pins a Laravel version, match the package to your SeAT release rather than to a fresh Laravel skeleton. There is no published compatibility matrix, so smoke-test on a staging SeAT instance first. Pin exact constraints in CI to catch dependency drift.
- How does eveseat/eseye sync characters, corporations, and alliances into EVE Eye?
- The plugin reads your authenticated SeAT characters together with their corporation and alliance affiliations, then pushes that identity data into EVE Eye. Syncs run as scheduled jobs and can also be triggered by hand with the package's artisan commands. EVE Eye then uses those identities to resolve map ownership, access, and channel permissions. Configurable group mappings translate SeAT structures into EVE Eye groups so the two stay aligned.
- Can I map SeAT roles, squads, corporations, and alliances to EVE Eye map and channel access?
- Yes: the package provides configurable group mappings for corporations, alliances, and squads that correspond to EVE Eye groups controlling map and channel access. That keeps permissions aligned with the roles you already manage in SeAT instead of duplicating them in EVE Eye. Re-run the sync after changing mappings so membership changes propagate to existing map owners.
- Where do I configure EVE Eye API credentials and sync options in eveseat/eseye?
- Credentials and options are set through a native SeAT settings screen, so you do not have to hand-edit environment files. The package also publishes a config file you can version for group mappings and sync behaviour. Keep EVE Eye API secrets out of version control and treat the stored settings as sensitive data.
- How do I run the EVE Eye sync manually or on a schedule?
- Scheduled sync jobs handle the routine work, so production hosts need a working Laravel scheduler and a queue worker. For one-off runs, debugging, or after bulk role changes, trigger the sync with the package's artisan commands. Manual runs are also useful right after new characters register in SeAT. Check the job and application logs for ESI or EVE Eye API failures rather than assuming a silent run succeeded.
- Is eveseat/eseye safe for production, and how are OAuth refresh tokens handled?
- Production use is viable but needs diligence: the OAuth refresh tokens involved are high-value, so verify they are encrypted at rest and scoped as narrowly as the package allows. The repository is listed as unknown with a modest star count, meaning there is no canonical upstream to audit, patch, or pin, which is a material supply-chain risk for anything touching authentication. Pin to a specific tag or commit, review the code before deployment, and keep a fallback client behind your own interface. Also account for ESI rate limits, endpoint deprecations, and the package's release hygiene.
- What licence is eveseat/eseye under, and can I use it in a commercial or closed-source project?
- The package is GPL-2.0, a copyleft licence, so redistributing it or bundling it into proprietary code can carry obligations you should review with legal. Internal use is generally fine, but SaaS-adjacent distribution or closed-source redistribution needs a licence read before you commit. Because the upstream repository is not clearly identified, confirm the licence file ships with the exact version you pin.
- Who maintains eveseat/eseye, and what are the alternatives if it is abandoned?
- It is a small community package with single-vendor gravity toward SeAT, so the maintainer bus factor and ESI drift are real concerns worth tracking in your dependency review. Alternatives include EVE Eye's own SSO and group management, a thin custom SeAT plugin that talks to the EVE Eye API directly, or a general ESI client such as eveseat/esi wrapped behind your own interface. Whichever you pick, keep the integration behind an internal port so swapping implementations is a config change rather than a rewrite.
Weaver
How can I help you explore Laravel packages today?