Download the PHP package yezzmedia/laravel-ops without Composer

On this page you can find all versions of the php package yezzmedia/laravel-ops. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of yezzmedia/laravel-ops

Informations about the package laravel-ops

Yezz Media

Latest Version PHP Version License

--- # Laravel Ops `yezzmedia/laravel-ops` is the shared operations panel package for the Yezz Media Laravel platform. It provides a Filament-based `/ops` panel with package, feature, diagnostics, audit, and access-facing operational surfaces on top of the normalized runtime exposed by foundation and, when installed, `yezzmedia/laravel-access`. ## Version Current release: `0.2.0` ## Requirements - PHP `^8.4` - Laravel `^13.0` components - `filament/filament ^5.0` - `spatie/laravel-package-tools ^1.93` - `yezzmedia/laravel-foundation ^0.1` Optional: - `yezzmedia/laravel-access ^0.1` for the preferred ops authorization and access-management workflows - `spatie/laravel-activitylog` for audit-facing surfaces - `spatie/laravel-health` for richer diagnostics posture - `yezzmedia/laravel-ops-analytics ^0.1` for analytics posture, tracker, and consent-aware surfaces inside the shared ops panel - `yezzmedia/laravel-ops-backups ^0.1` for backup posture and restore-readiness surfaces inside the shared ops panel - `yezzmedia/laravel-ops-infrastructure ^0.1` for infrastructure posture inside the shared ops panel - `yezzmedia/laravel-ops-sites ^0.1` for site inventory and assignment posture inside the shared ops panel - `yezzmedia/laravel-ops-security ^0.1` for security posture and governance surfaces inside the shared ops panel - `yezzmedia/laravel-ops-settings` for operator-managed settings UI inside the shared ops panel ## Installation Install the package in the consuming Laravel application: The service providers are auto-discovered: - `YezzMedia\Ops\OpsServiceProvider` - `YezzMedia\Ops\OpsPanelProvider` ## Configuration Publish the package config when you need to override panel defaults: Default configuration: ## What The Package Provides ### Shared ops panel shell `OpsPanelProvider` defines a dedicated Filament panel mounted at `/ops`. - uses the configured or resolved host auth guard - applies a dedicated ops authorization middleware boundary - registers the stable V1 ops pages and widgets - conditionally loads companion plugins when the corresponding packages are installed: - `YezzMedia\OpsAnalytics\Filament\OpsAnalyticsFilamentPlugin` - `YezzMedia\OpsBackups\Filament\OpsBackupsFilamentPlugin` - `YezzMedia\OpsInfrastructure\Filament\OpsInfrastructurePlugin` - `YezzMedia\OpsSites\Filament\OpsSitesFilamentPlugin` - `YezzMedia\OpsSecurity\Filament\OpsSecurityFilamentPlugin` - `YezzMedia\OpsSettings\Filament\OpsSettingsPlugin` ### Stable ops pages The package currently provides these operator-facing pages: - `OpsDashboard` - `PackagesPage` - `FeaturesPage` - `SystemHealthPage` - `AuditTrailPage` - `PermissionsPage` - `AccessManagementPage` The panel also registers detail pages that support drill-down workflows without adding extra top-level navigation entries: - `PackageDetailsPage` - `DoctorCheckDetailsPage` - `RoleDetailsPage` - `PermissionDetailsPage` - `AuditEntryDetailsPage` These surface the following routes: - `/ops` - `/ops/packages` - `/ops/features` - `/ops/diagnostics` - `/ops/audit` - `/ops/access/permissions` - `/ops/access/manage` ### Widgets and summaries The dashboard currently includes: - `InstalledPackagesWidget` - `FailingChecksWidget` - `RecentActivityWidget` These build on the package summary, diagnostics summary, and recent activity resolver layers instead of duplicating query or registry logic in widgets. ### Authorization model Ops declares a stable permission surface through foundation: - `ops.panel.access` - `ops.dashboard.view` - `ops.packages.view` - `ops.features.view` - `ops.diagnostics.view` - `ops.runtime.view` - `ops.audit.view` - `ops.access.view` - `ops.access.manage` When `yezzmedia/laravel-access` is not installed, ops falls back to reduced mode and uses the host-owned `viewOpsPanel` / `canAccessPanel()` boundary. When access is installed, the ops panel enforces the declared access permissions and unlocks the access-facing surfaces. ### Diagnostics and runtime posture `SystemHealthPage` and the diagnostics widget stack build on: - `RunSystemDiagnosticsAction` - `OpsDiagnosticsSummaryResolver` - `OpsDiagnosticsCacheManager` - `OpsRuntimePostureResolver` This keeps diagnostics collection and runtime posture aggregation in dedicated support classes instead of inside the page layer. ### Audit and access bridges `AuditTrailPage` uses the recent-activity resolver stack and degrades cleanly when no supported audit backend exists. `PermissionsPage` and `AccessManagementPage` use `OpsAccessBridge` to read from access-owned services rather than re-implementing permission-store or role-management logic inside ops. Those access-facing surfaces can: - inspect permission-store readiness - synchronize declared permissions - synchronize hinted roles - assign persisted roles to a user - remove persisted roles from a user The actual write operations remain delegated to access-owned runtime services. ## Foundation integration Ops registers itself with foundation through `OpsPlatformPackage`. That package descriptor currently provides: - package metadata for `yezzmedia/laravel-ops` - the stable ops permission declarations - an explicit ops-module surface, currently empty for V1 - security-governance declarations for the ops authentication entry point: - request `ops.request.auth.login-throttle` - requirement `ops.auth.login-throttle` These declarations are intentionally observe-only. Ops declares the required operator login-throttle posture, while verification stays in `yezzmedia/laravel-ops-security` and concrete runtime enforcement stays in the host auth and middleware layer. ## Development Available package scripts: ## License MIT

All versions of laravel-ops with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
filament/filament Version ^5.0
illuminate/contracts Version ^13.0
illuminate/support Version ^13.0
spatie/laravel-package-tools Version ^1.93
yezzmedia/laravel-foundation Version ^0.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package yezzmedia/laravel-ops contains the following files

Loading the files please wait ...