Weave Code
Waterline Laravel Package
durable-workflow/waterline
Waterline brings durable workflow execution to Laravel. Define multi-step workflows as PHP classes, run them reliably with retries and delays, and inspect progress from a database-backed store. Ideal for long-running background processes that must survive failures.
Operator UI for Durable Workflow runtime health, history, queues, retries, and repair.
Frequently asked questions about Waterline
- What is durable-workflow/waterline and is it a workflow engine?
- Waterline is a Laravel companion operator console for the Durable Workflow runtime, not the workflow engine itself. It gives you a UI for health, history, queues, retries, repair, schedule status, saved views, and backfills. Workflow execution is handled by the runtime, while Waterline provides the operational surface backed by a database store.
- How do I install Waterline in a Laravel application?
- Install it with composer require durable-workflow/waterline and rely on Laravel package auto-discovery. Then run php artisan waterline:publish to publish configuration and the prebuilt frontend assets, and gate the package routes behind your application's auth boundary. Asset publication is an explicit step on every upgrade, so put it in your deploy checklist rather than only in onboarding docs.
- Which Laravel and PHP versions does Waterline support?
- The provided context does not confirm a supported Laravel or PHP version matrix. It explicitly lists Laravel 10, 11, or 12 compatibility and the PHP version as open questions to verify. Test in a staging app before production, and confirm whether the package assumes Horizon, Redis, or a specific database driver.
- Does Waterline require the Durable Workflow runtime, and how tightly is it coupled to runtime internals?
- Yes, Waterline is a companion console for the Durable Workflow runtime and is not standalone. The biggest unknown is whether it integrates through a public API or directly against runtime table schema, and release 2.11.2 does not resolve that. Tight version coupling means a runtime minor bump could break the console, so confirm the required runtime version range first.
- How do I upgrade Waterline safely and avoid asset version skew?
- Update the Composer package, then re-run php artisan waterline:publish to refresh the prebuilt frontend assets and clear caches. A partial deploy where the package is updated but assets are not republished can leave the UI calling handlers that no longer match, causing silent failures during incidents. If you also use versioned service images, track the image tag and Composer package version as one unit.
- Are Waterline's repair, backfill, and schedule actions safe to run in production?
- These are privileged write paths with real blast radius, and backfill can replay a date range across workflows. The context does not confirm whether repair and backfill are idempotent, support dry runs, are audited, are reversible, or cap selection size. Treat them as risky operations, test them outside production first, and wrap the routes with your own authorization boundary.
- Does Waterline ship authorization gates or policies for its routes?
- Authorization behavior is not confirmed in the provided context. The evaluation asks whether Waterline ships gates and policies or whether you must wrap every route yourself, now including backfill and schedule routes. Plan to add your own middleware and route gating rather than assuming package defaults.
- What UI stack does Waterline use, and is waterline:publish re-runnable in CI?
- The context does not specify whether the UI is built with Blade, Livewire, or Inertia and Vue. It also does not confirm whether waterline:publish is idempotent or safe to re-run in CI, though prebuilt frontend assets ship in the release artifact. Verify publish behavior in a pipeline before automating it.
- What are the maintenance and community risks of adopting Waterline?
- Waterline has zero dependents and a low star count, so there is little third-party validation of upgrade paths or production hardening. Release 2.11.2 shows active maintenance through accessibility fixes and rebuilt assets, but that is not the same as broad ecosystem support. The MIT license and contained UI surface mitigate lock-in, with fork-and-own as the fallback.
- Can Waterline display workflow inputs and outputs, and does it support multi-tenant isolation or PII redaction?
- The context flags this as unresolved: workflow inputs and outputs, which may contain PII, could render in history views and saved views. Multi-tenant isolation and payload redaction are not confirmed. The read model, whether it uses live runtime tables or a separate history store, and retention are also unspecified, so confirm these before exposing the console broadly.
Weaver
How can I help you explore Laravel packages today?