Deployments
Package docs status
Section titled “Package docs status”This page is generated from public package documentation in capell-4/packages and the package manifest checked into the source repository.
| Field | Value |
|---|---|
| Composer package | capell-app/deployments |
| Package slug | deployments |
| Product group | Capell Operations |
| Tier | premium |
| Bundle | operations |
| Runtime contexts | admin, console |
| Capell version | ^4.0 |
| Source repository | capell-app/packages |
| Source path | packages/deployments |
| Docs source | packages/deployments/docs |
| Manifest | capell.json |
Repository deployment connections and Composer publishing for Capell CMS.
At A Glance
Section titled “At A Glance”- Package:
capell-app/deployments - Namespace:
Capell\Deployments\ - Surfaces: Filament admin, HTTP, database
- Service providers:
packages/deployments/src/Providers/DeploymentsServiceProvider.php - Capell dependencies:
capell-app/admin,capell-app/core - Third-party dependencies:
laravel/framework,lorisleiva/laravel-actions,spatie/laravel-data,spatie/laravel-package-tools
Why It Helps Your Capell Workflow
Section titled “Why It Helps Your Capell Workflow”- Helps operators connect repository providers and publish Composer requirement changes from Capell-managed workflows.
- Keeps deployment connection state and provider-specific behavior inside one package instead of scattering Git provider code.
- Gives developers Actions for validating OAuth state, preparing requirement commits, and publishing requirement changes.
Best Used With
Section titled “Best Used With”What It Adds
Section titled “What It Adds”- Repository deployment connections and Composer publishing for Capell CMS.
Built With
Section titled “Built With”This package makes its Composer dependencies visible because they are part of the value proposition, not just plumbing. When an upstream package has a public repository, its linked preview card points readers back to the maintainers so their work gets proper credit.
Capell packages used here
Open-source packages used here
- Laravel Actions - single-purpose action classes that keep package workflows out of controllers and Filament resources.
- Spatie Laravel Data - typed data objects for package boundaries, form state, settings, and structured results.
- Spatie Laravel Package Tools - Laravel package bootstrapping for config, migrations, commands, translations, and service provider setup.
Linked package previews
Screens And Workflow
Section titled “Screens And Workflow”Screenshots are generated from docs/screenshots.json during package deployment.
Code Map
Section titled “Code Map”| Area | Path | Purpose |
|---|---|---|
| Actions | packages/deployments/src/Actions | Domain operations. Test these directly where possible. |
| Data | packages/deployments/src/Data | Structured payloads, form state, view models, and integration data. |
| Enums | packages/deployments/src/Enums | Persisted states and Filament option values. |
| Models | packages/deployments/src/Models | Eloquent records owned by the package. |
| Filament | packages/deployments/src/Filament | Admin resources, pages, widgets, and settings UI. |
| HTTP | packages/deployments/src/Http | Controllers, middleware, and request handling. |
| Providers | packages/deployments/src/Providers | Registration, extension hooks, routes, migrations, and resources. |
| Resources | packages/deployments/resources | Views, translations, assets, and package resources. |
| Routes | packages/deployments/routes | Route files loaded by the service provider. |
| Config | packages/deployments/config | Package configuration and publishable config. |
| Database | packages/deployments/database | Migrations, seeders, and settings migrations. |
| Tests | packages/deployments/tests | Package-level Pest coverage. |
Admin Surface
Section titled “Admin Surface”- Pages:
DeploymentConnectionPage. - Widgets:
DeploymentConnectionWidget.
Runtime Surface
Section titled “Runtime Surface”- Controllers:
BitbucketCallbackController,GitHubCallbackController,GitLabCallbackController. - Routes:
packages/deployments/routes/oauth.php.
Data And Persistence
Section titled “Data And Persistence”- Models:
DeploymentConnection. - Migrations:
2026_05_10_190845_01_create_deployment_connections_table.php. - Config:
packages/deployments/config/capell-deployments.php. - Data objects live in
src/Data/; use them for payloads, form state, and view models.
Extension Points
Section titled “Extension Points”- Contracts:
GitProviderContract,PublishesComposerChanges. - Register Capell extension points, routes, migrations, settings, render hooks, and resources from service providers.
Install And Setup
Section titled “Install And Setup”- Install with
composer require capell-app/deploymentsin the host Capell application. - Run migrations through the host application package install flow.
- In this repository, verify package changes with
vendor/bin/pest; do not usephp artisan.
Testing
Section titled “Testing”Run package tests from the repository root:
vendor/bin/pest packages/deployments/tests --configuration=phpunit.xmlMaintenance Notes
Section titled “Maintenance Notes”- Put behaviour changes in
src/Actions/; UI classes, commands, and controllers should call actions instead of owning domain logic. - Use package
Dataclasses at boundaries instead of passing anonymous arrays between layers. - Use backed enums for persisted values and enum labels for Filament options.