- What is lartisan/ploi-dashboard and what does it do?
- It is a Laravel package that adds a Filament panel for managing Ploi hosting. It shows servers, sites, and deployments at a glance, surfaces health information, and lets you run common Ploi actions without leaving your Laravel admin. Architecturally it is a thin, read-mostly UI layer over the Ploi API, so it does not own persistent domain state.
- How do I install lartisan/ploi-dashboard in a Laravel app?
- Install it with Composer, register the plugin on an existing Filament panel, supply a Ploi API token, and publish the config file. The integration sequence is: pin the package version whose Filament constraint matches your host app, register the plugin, provision a scoped Ploi token, then publish and review the config. Effort is measured in hours, not sprints, provided Filament is already part of your application.
- Does lartisan/ploi-dashboard require Filament, or does it work in plain Laravel?
- It requires a Filament panel in addition to PHP 8.x and Laravel. If your application does not already use Filament, adopting this package means adopting Filament first, which is a much larger decision. Confirm Filament is already a dependency before scoping any dashboard work.
- Which Filament versions does lartisan/ploi-dashboard support, including Filament 5?
- Version 2.1.1 added a Filament 5 support PR, but the release notes do not make clear whether it widens the Composer constraint to support Filament 3, 4, and 5 concurrently or replaces older majors. Check the composer.json require block before planning around it. If your host app is on Filament 4, verify that the constraint still permits it and confirm whether a maintained branch exists for that major.
- How do I configure the Ploi API token, and can I scope it read-only?
- The package needs a Ploi API token, which is stored in your application config or environment and therefore sits inside the blast radius of any app compromise. Ask which Ploi API scopes the package actually uses and whether a read-only token is sufficient for your use case. Prefer the narrowest token scope that still allows the dashboard actions you need.
- Is lartisan/ploi-dashboard safe to use in production?
- It is architecturally cheap to adopt and equally cheap to remove because it is a thin UI layer over the Ploi API rather than a system of record. The main production concern is the account-level Ploi API token landing in your config and env files, so treat it as sensitive credential material. Also pin the package version and review Filament compatibility before upgrading, since it is a single-maintainer community package.
- Does upgrading to lartisan/ploi-dashboard v2.1.1 require migrations or config changes?
- No. It is a patch release with no migrations, no config schema changes, and no announced deprecations for existing installs on v2.1.0. The substantive runtime change is the Filament 5 support PR, while the remaining commits are Dependabot updates to CI-only tooling.
- Can lartisan/ploi-dashboard replace my deployment pipeline or infrastructure-as-code?
- No. It is an operator convenience layer for viewing servers, sites, and deployments and running common Ploi actions from a panel. It is not a substitute for infrastructure-as-code or an automated deployment pipeline. Use it to reduce context switching, not to manage repeatable infrastructure or release processes.
- How is lartisan/ploi-dashboard maintained, and how risky are Filament upgrades?
- It is a single-maintainer community package that has started accepting outside contributions, and the Filament 5 support PR came from a first-time contributor, which is a mild positive signal but also suggests the maintainer is not the one tracking Filament releases. Filament moves quickly, so a plugin whose headline feature is support for the new major is structurally always playing catch-up. Expect a window after each Filament major where this package is pinned or broken, and ask whether the Filament 5 PR has rendering test coverage rather than only green CI.
- What are the alternatives to lartisan/ploi-dashboard?
- You can use Ploi's own dashboard directly, build a small custom Filament page against the Ploi API, or use a comparable hosting panel integration if your infrastructure lives elsewhere. This package mainly saves context switching for teams already standardized on Filament for internal admin surfaces. If you do not have a Filament panel, the cost of adopting one should be evaluated on its own merits before adding this plugin.