- What is novay/minios and what does it actually add to a Laravel app?
- novay/minios is a Composer package for Laravel that ships a web desktop environment — a UI shell with a window manager, launcher and panel — inside your existing application rather than as a separate SPA. It runs within the host app's routing, authentication, session and asset pipeline. The v0.1.0 release is described as a first unified release with intent only, so the exact feature set and public API are not yet documented.
- How do I install novay/minios in a Laravel application?
- Installation follows the standard Laravel package pattern: composer require novay/minios, let service provider auto-discovery register the package, then run vendor:publish for any config and assets. Beyond that, nothing is documented in the release notes, so treat the install as a spike rather than a copy-paste recipe. Pin the version to 0.1.* rather than a caret range while you evaluate.
- Which PHP and Laravel versions does novay/minios support?
- The current release notes do not state a supported PHP or Laravel version matrix. Before committing, check the package's composer.json constraints and confirm the support window with the maintainer. Until that is verified, assume no compatibility guarantee and test on your exact PHP and Laravel combination.
- Does novay/minios require Livewire, Inertia, Vue or React?
- Unconfirmed. A desktop-shell UI almost certainly depends on a specific component stack and a front-end build step, such as Vite with Livewire or Inertia plus Vue or React, but the release notes say nothing about it. If the package ships source assets rather than prebuilt ones, every developer machine and CI runner inherits that toolchain. Confirm this during your spike before rolling it out to a team.
- Is novay/minios an MinIO or S3 object storage package?
- The name is easy to confuse with MinIO object storage, and some package descriptions circulate that imply S3-compatible file handling. The repository itself describes the package as a web desktop environment for Laravel, which is a completely different purpose. Verify the actual source and dependencies before adding it to a project, and never assume it gives you upload or storage APIs.
- Does novay/minios replace my application's Blade layout or mount alongside it?
- This is one of the key unanswered architecture questions. The package could either take over your layout or register itself as a route group that sits next to your existing admin surface. Until it is confirmed, keep your current Blade and admin paths untouched and mount novay/minios behind a feature flag or non-production route group so it can be removed with a config change.
- Is novay/minios safe to run in production?
- Version 0.1.0 is pre-stability with no upgrade guide, deprecation policy or documented permission layer. Desktop metaphors typically involve file browsers, editors or task runners, each of which is a path-traversal, privilege-escalation or remote-code-execution concern if authorization is not explicitly modelled. Do not expose it to production users until you have reviewed how individual applications and any file or terminal widgets are gated, and confirmed how it behaves on mobile and with assistive technology.
- Can I use novay/minios alongside Filament, Nova or Backpack?
- There is no documented compatibility story with existing Laravel admin panels. In practice novay/minios is a competing admin surface, not a complement to Filament, Nova or Backpack, so running both means two systems of record for internal tooling. Decide which one owns your admin routes before writing any code.
- How do I handle updates and breaking changes in novay/minios?
- As a pre-1.0 package, semver permits breaking changes in any minor release, and there is currently no upgrade guide or deprecation policy. Pin the exact version you evaluate, such as 0.1.*, and review the diff of any bump before applying it. Keep the package isolated behind a flag so a breaking release can be rolled back quickly.
- Is novay/minios actively maintained and what licence does it use?
- The repository does not state a licence, maintainer count, roadmap or support commitment, so the bus factor is unknown. A one-line changelog for the first unified release is not enough evidence of a stable release cadence. Ask the maintainer about licence terms, expected release cadence and support before any long-term commitment.