PHPackages                             devoption/beacon - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [DevOps & Deployment](/categories/devops)
4. /
5. devoption/beacon

ActiveLibrary[DevOps & Deployment](/categories/devops)

devoption/beacon
================

Production-ready Docker and Helm support for Laravel applications, with guided installation, Octane integration, and streamlined build/deploy workflows.

v1.0.1(1mo ago)12↑2900%[6 issues](https://github.com/devoption/beacon/issues)MITPHPPHP ^8.3CI passing

Since Apr 5Pushed 1mo ago1 watchersCompare

[ Source](https://github.com/devoption/beacon)[ Packagist](https://packagist.org/packages/devoption/beacon)[ Docs](https://github.com/devoption/beacon)[ RSS](/packages/devoption-beacon/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (6)Dependencies (7)Versions (3)Used By (0)

Beacon
======

[](#beacon)

Production-ready Docker and Helm support for Laravel applications, with guided installation, Octane integration, and streamlined build and deploy workflows.

What Beacon does
----------------

[](#what-beacon-does)

Beacon installs into an existing Laravel application and scaffolds the first layer of production deployment assets.

Current MVP features:

- interactive `php artisan beacon:install` command built with Laravel Prompts
- optional Laravel Octane installation when the Octane runtime is selected
- Dockerfile generation for `php-fpm` or `octane`
- Helm chart scaffolding under `charts/`
- named Helm environment overlays for `local`, `staging`, and `production`
- managed Composer scripts for `beacon:build` and `beacon:deploy`
- Pest coverage, Laravel compatibility CI, and automated semantic releases for the package itself

Out of scope for this MVP:

- cloud-specific deployment logic
- full platform provisioning
- environment-specific infrastructure assumptions

Requirements
------------

[](#requirements)

- PHP `^8.3`
- Laravel `^11.0 | ^12.0 | ^13.0`

Install
-------

[](#install)

Recommended as a development dependency in the Laravel application you want to prepare:

```
composer require devoption/beacon --dev
```

Then run the installer:

```
php artisan beacon:install
```

Install flow
------------

[](#install-flow)

Beacon currently prompts for:

- application name
- runtime: `php-fpm` or `octane`
- deployment scaffolding: `docker`, `helm`, or `docker-and-helm`
- ingress provider: disabled, Ingress NGINX, or Traefik
- secret handling: Beacon-managed Helm secret or an existing Kubernetes secret
- whether Beacon should update Composer scripts

When the Octane runtime is selected, Beacon checks the target application's `composer.json` and installs `laravel/octane` if it is not already present.

Generated files
---------------

[](#generated-files)

Depending on the options you choose, Beacon generates:

- `Dockerfile`
- `charts//Chart.yaml`
- `charts//values.yaml`
- `charts//values.local.yaml`
- `charts//values.local.secrets.example.yaml`
- `charts//values.staging.yaml`
- `charts//values.staging.secrets.example.yaml`
- `charts//values.production.yaml`
- `charts//values.production.secrets.example.yaml`
- `charts//templates/_helpers.tpl`
- `charts//templates/deployment.yaml`
- `charts//templates/secret.yaml`
- `charts//templates/service.yaml`
- `charts//templates/ingress.yaml`

If Composer script updates are enabled, Beacon also manages:

- `beacon:build`
- `beacon:deploy`

Example managed scripts:

```
{
  "scripts": {
    "beacon:build": "docker build --file Dockerfile --tag my-app:latest .",
    "beacon:deploy": "@php artisan beacon:deploy"
  }
}
```

Beacon generates `values.yaml` as the shared chart values file and also creates environment-specific overlays for `local`, `staging`, and `production`. The selected ingress strategy is persisted there so the generated chart knows whether ingress is disabled and which class name Beacon should prepare for. The deploy command always applies `values.yaml` first, then layers the selected environment values file on top when it runs Helm.

Sensitive application values are kept out of the committed environment overlays. Beacon now:

- keeps non-sensitive settings in the regular `values*.yaml` files
- generates `values..secrets.example.yaml` templates to show the expected secret structure
- adds `/charts/*/values.*.secrets.yaml` to the Laravel app `.gitignore`
- automatically includes `values..secrets.yaml` during `beacon:deploy` when that ignored file exists

This keeps secret values out of Git-tracked files, but it does not keep them out of Helm release metadata. When `values..secrets.yaml` is passed to Helm, those values are stored in the Helm release Secret or ConfigMap and can remain in release history.

If you choose the existing Kubernetes secret mode during installation, Beacon configures the chart to reference that external secret instead of creating its own Secret manifest. Use that mode, or another workflow that injects secrets outside Helm values files, if you need to avoid persisting secret values in Helm release metadata or history.

Rerunning the installer
-----------------------

[](#rerunning-the-installer)

Beacon is designed to be rerunnable.

- generated Beacon-managed files are rewritten with current stub output
- unchanged generated files remain unchanged on repeat runs
- Beacon-managed Composer script entries are updated without replacing unrelated user scripts

Development
-----------

[](#development)

Run the test suite with:

```
composer test
```

Repository automation also includes:

- Laravel compatibility CI in [`.github/workflows/ci.yml`](https://github.com/devoption/beacon/blob/main/.github/workflows/ci.yml)
- publish-readiness validation in [`.github/workflows/publish-readiness.yml`](https://github.com/devoption/beacon/blob/main/.github/workflows/publish-readiness.yml)
- automated semantic releases in [`.github/workflows/release.yml`](https://github.com/devoption/beacon/blob/main/.github/workflows/release.yml)

For contributor workflow details, see [CONTRIBUTING.md](CONTRIBUTING.md).

For maintainer release and Packagist setup notes, see [docs/RELEASING.md](https://github.com/devoption/beacon/blob/main/docs/RELEASING.md).

License
-------

[](#license)

[MIT](LICENSE)

###  Health Score

35

—

LowBetter than 80% of packages

Maintenance71

Regular maintenance activity

Popularity5

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity50

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

2

Last Release

46d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/f454b0cd60400133db60c24393f14f476c183b7fa709dd83c747ed1d753dee96?d=identicon)[iBourgeois](/maintainers/iBourgeois)

---

Top Contributors

[![ibourgeois](https://avatars.githubusercontent.com/u/3633464?v=4)](https://github.com/ibourgeois "ibourgeois (27 commits)")

---

Tags

laravellaravel-packagedockeroctanedeploymentkuberneteshelm

###  Code Quality

TestsPest

Code StyleLaravel Pint

### Embed Badge

![Health badge](/badges/devoption-beacon/health.svg)

```
[![Health](https://phpackages.com/badges/devoption-beacon/health.svg)](https://phpackages.com/packages/devoption-beacon)
```

###  Alternatives

[timokoerber/laravel-one-time-operations

Run operations once after deployment - just like you do it with migrations!

6471.7M11](/packages/timokoerber-laravel-one-time-operations)[thecodeholic/laravel-hostinger-deploy

Laravel package for automated Hostinger deployment with GitHub Actions support

565.3k](/packages/thecodeholic-laravel-hostinger-deploy)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)