- What is zeeshanu/opus used for?
- Opus is described as a Laravel package that adds customizable maintenance mode, with a polished offline page and a secret-token bypass for trusted users. The repository overview also calls it an open source knowledge base application for Teams, so the current README and release notes should be treated as the source of truth. It is not a headless library; it ships both backend service code and a UI surface.
- How do I install zeeshanu/opus with Composer?
- Install it with composer require zeeshanu/opus and rely on Laravel package auto-discovery for the service provider. Publish the package config and any views or assets using the vendor:publish command documented by the package. If the package owns database tables, publish and run its migrations before enabling the UI or maintenance behavior.
- Which Laravel and PHP versions does Opus support?
- The available notes do not list a Laravel version range, PHP version floor, or dependency constraints. Confirm support from composer.json, the README, and the CI matrix before assuming compatibility with your Laravel major. This is the largest evaluation gap because version floors often move between patch releases.
- How does the secret-token bypass for maintenance mode work?
- Opus is described as letting trusted users bypass maintenance mode with a secret token, which is useful for staging checks and pre-release verification. The exact token configuration key, query-string or cookie behavior, and authorization rules are not specified in the available notes. Confirm the bypass mechanism in the package documentation before relying on it in production.
- Does Opus ship routes, views, and an admin UI?
- The evaluation indicates Opus ships both backend service classes and an opinionated admin surface, including routes, controllers, and likely Blade, Livewire, or Inertia views. That means adoption couples your application to the package's routing, view, and authorization conventions, not just to a PHP API. If you only want the service layer, plan to disable or avoid registering the UI portions.
- What changed in Opus v1.3.5, and what are the delete semantics?
- Version 1.3.5 is a patch release that reportedly includes a UI refresh and CRUD expansion for integration records, adding delete and update support. The notes do not confirm whether deletes are soft or hard, whether they cascade through foreign keys, or whether restore and bulk delete exist. Treat delete semantics as the highest-risk item and verify behavior before upgrading existing installs.
- Does Opus handle authorization for update and delete actions?
- The available assessment does not confirm whether Opus ships policies or gates for its new delete path or defers to host-application authorization. A new delete route in a UI-enabled package is a privilege-escalation vector unless authorization is explicitly delegated or enforced. Review the package middleware, policies, and route definitions before enabling it for non-admin users.
- Will upgrading Opus break published views or configuration?
- The notes describe a UI refresh and CRUD expansion shipped as a patch release, but they do not specify whether published Blade views, routes, config keys, or migration files changed. Overridden Blade views are a common silent breakage point in Laravel packages, so diff your published assets against the new release. Test in a staging copy and check for a changelog or upgrade guide beyond the two-line note.
- How should I test Opus before production rollout?
- Add a staging environment that exercises installation, config publishing, migrations, the maintenance page, token bypass, and the integration update and delete paths. Cover authorization and delete semantics with feature tests because those are the highest-risk areas. The notes do not report test coverage or a CI matrix, so inspect the package own tests and known issues before relying on it.
- What are alternatives to Opus for Laravel maintenance mode?
- Laravel's built-in php artisan down command and custom middleware are the baseline alternatives for maintenance mode. Third-party maintenance-mode packages can add polished pages and bypass tokens, but compare Laravel version support, authorization, published-view stability, and configuration before choosing. If you only need the maintenance behavior, prefer the smallest package that documents its bypass and version constraints.