- What is jeffersongoncalves/filament-satis and what problem does it solve?
- Filament Satis is a Filament plugin that brings your private Satis Composer repository into the admin panel. Instead of editing satis.json by hand or SSH-ing into the server, you get a themed interface to browse hosted packages, inspect available versions and metadata, and keep private dependencies organized. It is aimed at Laravel teams already running Filament as an internal ops console alongside a private Composer registry.
- How do I install filament-satis in a Laravel application?
- Install it with composer require jeffersongoncalves/filament-satis, then register the plugin in your panel provider's plugin() call. Publish and adjust the package configuration so repository paths and access settings point at your Satis workspace. Check the composer.json of the release you install to confirm the Laravel and Filament version constraints match your app before deploying.
- Does this plugin require Filament, or can I use it in a plain Laravel app?
- It requires Filament, because it is a panel plugin rather than a standalone package. If you are not already running Filament, adopting this package effectively means adopting Filament first, and that is the real architectural decision. Teams that already have a Filament admin panel only add a small marginal dependency.
- Do I need an existing Satis repository before installing the plugin?
- Yes. The plugin works with existing Satis setups and expects a reachable Satis workspace and generated repository output. You do not need to migrate your Composer configuration or change your existing publishing pipeline. Install it against a scratch Satis workspace first to confirm it reads your layout correctly.
- Does the plugin run the Satis binary, or does it only edit configuration?
- The plugin is a UI layer on top of Satis: it surfaces packages, versions and configuration rather than replacing Composer or the Satis runtime itself. Where build or rebuild actions are exposed in the panel, they can touch your Satis workspace, so verify exactly what executes and with which privileges. Confirm sandboxing and filesystem permissions before pointing it at a production workspace.
- Can I translate filament-satis or override the translations it ships with?
- Version 1.13.0 added a large set of locales, which lowers the adoption barrier for non-English teams. Translation coverage per locale and the quality of Composer-specific terminology should be spot-checked before enabling broadly, especially on action labels for build and delete operations. Check whether the translation files can be published via vendor:publish and overridden in your app's lang directory so you can fix wording without forking the package.
- Will using filament-satis break my existing Composer installs or CI pipelines?
- No. The plugin is additive and does not change how Composer consumes your repository, so CI pipelines and developer workstations keep using the same repository URL. No database migrations or config schema changes are required beyond registering the plugin. The safest pattern is to keep the Satis CLI as the source of truth and treat the UI as a convenience layer.
- How should I test filament-satis before rolling it out to production?
- Pilot it in a non-production Filament panel, or a dedicated staging panel provider, pointed at a scratch Satis workspace. Verify that the Satis configuration it produces matches what your current pipeline generates, either byte-for-byte or semantically. If the output diverges, keep the CLI workflow authoritative and use the plugin read-mostly until you are confident.
- What are the alternatives to using this plugin for managing private Composer packages?
- The direct alternatives are hand-editing satis.json and rebuilding with the Satis CLI, or paying for a hosted service such as Private Packagist. Building your own small Filament resource is another option, but it duplicates what this package already provides. Choose filament-satis if you already have Filament and want the admin UI without leaving your existing Satis setup.
- Is filament-satis actively maintained, and what is its bus factor?
- Contribution is concentrated around one maintainer plus an i18n contributor, which is a continuity concern for a package that touches build tooling. Dependabot group bumps and standardized test and changelog workflows are positive signals, and the 1.12 to 1.13 upgrade is additive with no signaled deprecations or migrations. Mitigate the risk by pinning a version you have validated and documenting a fallback to running Satis via the CLI; also confirm the license in composer.json against your distribution constraints.