Weave Code
Web Laravel Package
seatplus/web
Seatplus Web is the Laravel-powered frontend for the Seatplus ecosystem, providing authentication, dashboards, and management screens for EVE Online communities. It integrates with Seatplus backend packages to surface member, fleet, and corporation data in a customizable web UI.
Web frontend of seatplus
Frequently asked questions about Web
- What is seatplus/web and what does it actually add to a Laravel app?
- Seatplus Web is the web layer of the Seatplus platform, packaged as a Composer dependency for Laravel. It wires routes, controllers, and Blade views into your application so you get the core Seatplus screens without writing them yourself. It sits on top of the Seatplus core packages and surfaces member, fleet, and corporation data through a cohesive interface.
- How do I install seatplus/web with Composer?
- Install it as a normal Composer dependency with composer require seatplus/web. Because it ships Laravel package discovery metadata, the service provider is registered automatically, so no manual edits to config/app.php are required on modern Laravel versions. After that, run your migrations and publish the package assets and settings as needed.
- Which Laravel and PHP versions does seatplus/web support?
- Support depends on the version you install, so always check the require constraints in the package's composer.json before upgrading. The package is built around Laravel conventions such as service providers, middleware, and Blade, so it targets the framework versions listed there. Pinning a specific release in composer.json is the safest way to stay within a supported combination.
- Do I need the Seatplus core packages installed before seatplus/web?
- Yes. Seatplus Web is the presentation layer and depends on the Seatplus backend packages for data and domain logic. Installing it alone will not give you a working platform, because the member, fleet, and corporation data comes from the core packages. Composer will normally pull in the required dependencies, but the platform still needs to be configured as a whole.
- How do I publish the config and assets for seatplus/web?
- The package exposes publishable assets and settings, which you register with the standard Laravel vendor:publish command. Run php artisan vendor:publish and select the Seatplus Web provider tag to copy configuration and frontend assets into your application. Once published, those files live in your project and can be edited freely.
- Can I customize the Blade views and layouts that ship with the package?
- Yes. The views are Blade templates built to match the platform UI, and you can publish them and override them in your own resources/views directory. Laravel's view resolution lets your application's copies take precedence over the package defaults. That makes it practical to rebrand layouts or adjust individual screens without forking the package.
- How does authentication and authorization work in Seatplus Web?
- Seatplus Web integrates with the Seatplus authentication and authorization middleware rather than implementing its own login flow. Access to the management screens is therefore governed by the Seatplus user and permission model, which is built around EVE Online accounts. Make sure the auth middleware from the core packages is registered and applied before exposing the routes publicly.
- How do I override or disable the routes registered by seatplus/web?
- The package registers its routes through its service provider, so route customisation is usually done by adjusting the published configuration or by registering your own routes with higher priority. If you need full control, you can conditionally disable the package's route loading in your application's provider. Review the routes file in the package first to see which names and prefixes it expects.
- Is seatplus/web suitable for production use?
- It is intended to be installed as a standard Composer dependency in a real Laravel application, so it follows normal production deployment practices. You should still cache your configuration and routes, compile assets, and verify that the Seatplus core services and queue workers are running. Test the full authentication and authorization flow in a staging environment before going live, since the web layer depends heavily on the core packages.
- Can I use seatplus/web without an EVE Online community, or is there an alternative?
- The package is purpose-built for EVE Online communities, so its screens assume Seatplus member, corporation, and fleet data from ESI-backed core packages. If you do not need that domain, a generic Laravel admin starter or a simpler dashboard package will be less overhead. For EVE groups specifically, keeping the Seatplus web and core packages together is the intended setup.
Weaver
How can I help you explore Laravel packages today?