Weave Code
Docking Laravel Package
shipsaas/docking
Docking is a Laravel package for SaaS billing and subscription management. It gives you a simple way to define plans, gate features, and handle subscriptions, making it easier to add paid tiers and customer billing to your Laravel application.
DocKing: Your shared-microservice that takes over the document templates management & render/export PDF
Frequently asked questions about Docking
- What is shipsaas/docking used for in a Laravel app?
- shipsaas/docking is tied to DocKing, a shared microservice for managing document templates and rendering or exporting PDFs. The technical assessment describes it as a containerized Laravel runtime distribution rather than a conventional application library, shipping both PHP-FPM and Octane Docker images. Use it when you want a packaged Laravel runtime for DocKing-style document workflows, not as a drop-in billing SDK.
- How do I install shipsaas/docking in a Laravel project?
- You can require the package with composer require shipsaas/docking, but the technical assessment treats production adoption as an image substitution rather than a code-level migration. Pin the current Docker image digest before evaluating v1.4.3, then run it with your existing environment variables, volumes, and entrypoint overrides in a non-production environment. Do not rely on latest tags if you need reproducible deployments.
- Does Docking support Laravel Octane?
- Yes. The package ships an Octane image alongside its FPM image and pins laravel/octane. Verify the Octane version delta before upgrading, because worker lifecycle and PHP extension requirements can change between Octane releases. Run your existing queue, listener, and long-running worker tests against the new image.
- Which Laravel and PHP versions does shipsaas/docking support?
- The provided context does not include a full PHP and Laravel support matrix for the FPM or Octane variants. The technical assessment flags that matrix as a key question to confirm before adoption. Check the repository release notes and image tags for the exact versions supported by v1.4.3.
- How does Docking handle logs in production?
- Version 1.4.3 emits logs to stdout and stderr in both the FPM and Octane images. If your infrastructure tails storage/logs with Fluent Bit, sidecars, logrotate, or volume mounts, re-point collection to the Docker logging driver or an equivalent collector. This logging change is the most likely source of post-upgrade incidents, so test it before production.
- What are the SQLite permission issues with Docking containers?
- Docking includes SQLite permission ergonomics and discloses the container UID/GID. Confirm that the UID/GID is deterministic across builds and architectures before you chown SQLite files or volumes to that value. If the user ID changes on the next image pull, file ownership can break.
- Can I use Docking with my company's golden base images or Helm charts?
- Fit is weak where your platform team mandates its own base images, Helm charts, or PaaS runtime. Docking owns the Dockerfile and runtime layer, so it can conflict with an established golden image or entrypoint abstraction. Use it only if you are comfortable letting the package own part of your platform supply chain.
- How should I migrate from my current Laravel image to Docking v1.4.3?
- Treat it as an image substitution, not a code migration. Pin your current image digest, stand up v1.4.3 in non-production with the same env vars, volumes, and entrypoint overrides, then diff PHP extensions, Octane worker flags, log destination, and container user. Promote to staging and production only after parity checks pass.
- Is shipsaas/docking a SaaS billing and subscription package?
- The available technical assessment and repository description point to DocKing document template management and PDF export packaged as a containerized Laravel runtime, not a billing or subscription API. The billing blurb appears inconsistent with that assessment. If you need paid tiers and subscription billing, evaluate dedicated Laravel billing packages instead.
- Is shipsaas/docking actively maintained and safe for production?
- Version 1.4.3 is an operational patch release that bumps laravel/octane, adds stdout/stderr logging, and discloses UID/GID for SQLite ownership. Before production, confirm release cadence, immutable image tags, image signing, scanning, and SBOMs, since patch releases can change runtime behavior without application code changes. Pin digests and audit the Dockerfile or upstream base image.
Weaver
How can I help you explore Laravel packages today?