Weave Code
Seat Laravel Package
eveseat/seat
EVE SeAT is an open-source Laravel-based management and authentication platform for EVE Online corporations and alliances, offering member management, API key handling, fleet tracking, and extensible integrations.
SeAT (Simple EVE API Tool) is an open-source, Laravel-based management platform for EVE Online corporations and alliances. It aggregates character, corporation, and alliance data from the ESI API into a single self-hosted dashboard, giving leadership clear insight into membership, activity, and assets.
- ESI integration for characters, corporations, and alliances
- Role-based access control with granular permissions
- Character and member tracking with token management
- Scheduled jobs and queues for reliable data refreshes
- Modular architecture for extending with plugins and themes
Frequently asked questions about Seat
- What is eveseat/seat used for in Laravel applications?
- eveseat/seat is an open-source Laravel platform for EVE Online corporation and alliance management. It provides API key handling, roles and permissions, HR, intel, and fleet tooling for leaders and members. Teams already using PHP and Laravel can run it as an operations platform rather than a small utility package.
- How do I install SeAT with Composer?
- Install eveseat/seat through Composer and follow the project’s official installation guide for database, environment, queue, and scheduler setup. Because SeAT is a full Laravel platform, pay attention to .env configuration and any publishable assets or migrations. Confirm PHP and Laravel constraints in composer.json before starting.
- Which Laravel and PHP versions does SeAT 5.x support?
- The provided release context does not list exact PHP or Laravel version constraints for SeAT 5.0.1. Check composer.json and the official documentation for the supported PHP and Laravel ranges before upgrading. Also confirm that your SeAT plugins or modules support the same versions.
- How do I upgrade SeAT from 5.0.0 to 5.0.1?
- Treat it as a routine patch upgrade through the normal Composer update path from 5.0.0 to 5.0.1. Rebuild Laravel caches if your deployment standard requires it, and compare effective config output before and after the update. Run application smoke tests plus queue worker and scheduler checks before production rollout.
- What changed in SeAT 5.0.1 default environment settings?
- The only release-note detail is PR #902, add default env settings, which suggests a configuration or default-value change rather than a feature or data-model change. Review the PR diff to determine whether the defaults are documentation-only, config-only, or runtime behavior. Treat the assessment as provisional until that diff and configuration precedence are confirmed.
- Do SeAT 5.0.1 defaults override my existing .env values?
- The release notes do not state whether the new defaults override existing .env values or only fill missing ones. Test in staging with a copy of your production .env, including intentionally unset variables, and compare effective Laravel config before and after upgrade. Confirm precedence between .env, published config files, and package defaults before deploying.
- Is SeAT 5.0.1 safe for production?
- SeAT 5.0.1 appears to be a low-complexity patch release, but production safety depends on whether the new defaults are safe for secrets, debug mode, queue, cache, and database settings. Validate default precedence and ensure production .env values are not unexpectedly overridden. Use a rollback plan and rebuild config cache as part of deployment.
- How should I test a SeAT patch upgrade before deploying?
- Use staging with a copy of production .env and intentionally unset variables to reveal default-value behavior. Compare effective Laravel config before and after the upgrade, then run smoke tests for authentication, API keys, roles, queues, scheduler, and SeAT-specific integrations. Only promote to production after confirming no config cache or startup issues.
- Will SeAT 5.0.1 break existing plugins or modules?
- No breaking changes, schema migrations, or public API changes are indicated in the release notes for 5.0.1. Still confirm composer.json constraints and check whether any plugins or modules depend on env keys that are now defaulted. Test those integrations in staging before upgrading production.
- What are alternatives to SeAT for EVE Online corporation management?
- Alliance Auth is a common alternative for EVE Online community management, but compare tools by Laravel/PHP fit, API coverage, plugin ecosystem, and maintenance effort. SeAT is a strong fit for teams already standardized on Laravel and needing corporation, alliance, HR, intel, and fleet tooling. Evaluate upgrade cadence and configuration transparency before choosing.
Weaver
How can I help you explore Laravel packages today?