- What is micro-module/enqueue-fs?
- It is a filesystem transport adapter for Enqueue, the PHP messaging abstraction. It stores queued messages as files on local disk so PHP apps can produce and consume messages without Redis, RabbitMQ, or another broker. It is intended for lightweight, low-volume asynchronous work, testing, and simple single-node setups. It is not a native Laravel queue driver.
- Does micro-module/enqueue-fs work with Laravel queues out of the box?
- No, Laravel fit is indirect. You would need a custom Laravel queue connector, a service provider, or a standalone Enqueue worker command. The package metadata does not document Laravel integration, so expect to write glue code and contract tests. Keep it behind an application-owned dispatch interface so you can swap transports later.
- How do I install micro-module/enqueue-fs with Composer?
- Install it as a Composer dependency using the package name micro-module/enqueue-fs, alongside a compatible enqueue/enqueue version. Composer installation is likely straightforward, but you must confirm autoloading, supported PHP versions, and Enqueue version constraints. Pin the package version and commit in production because community validation is negligible.
- Which PHP and Laravel versions are supported by micro-module/enqueue-fs?
- The provided metadata does not document supported PHP or Laravel versions. You must verify Composer constraints, PHP extensions, and Enqueue compatibility before adoption. For Laravel, validate the worker lifecycle and queue contract mapping on your target version. Do not assume current Laravel support without a spike.
- Does micro-module/enqueue-fs support ack/nack, retries, delayed messages, and dead-lettering?
- The package is a filesystem transport, so behavior depends on the underlying Enqueue transport implementation and its capabilities. The assessment flags ack/nack, retries, delayed messages, dead-lettering, and visibility timeouts as key questions to verify. Test each behavior explicitly with contract tests before relying on it. Do not assume production-grade failure handling without evidence.
- Is micro-module/enqueue-fs safe for multi-node or high-throughput production messaging?
- No, it is a poor strategic fit for high-throughput, multi-tenant, or multi-node production messaging. Filesystem transports raise concerns around atomicity, locking, visibility timeouts, duplicate or lost deliveries, and shared-volume or NFS semantics. The package also has 0 stars and 0 dependents, indicating negligible community validation. Use it only for tactical, non-critical pilots or single-node low-volume work.
- What are the operational risks of using a filesystem queue in Laravel?
- Risks include filesystem atomicity, locking, stale message cleanup, disk retention, poison-message handling, and observability gaps. If the spool directory is on shared storage or container-mounted volumes, test the exact target filesystem for locking and rename semantics. Secure and monitor the spool directory because queued payloads may contain sensitive data. Plan alerts, retention, and dead-letter handling before any production pilot.
- Can I use micro-module/enqueue-fs for testing and CI?
- Yes, that is one of the better fits because it avoids external broker infrastructure in tests and CI. It can also suit local development and offline or edge jobs where a broker is impractical. Still pin the version and test dispatch, consume, retry, fail, cleanup, and worker restart behavior. Treat it as a development convenience rather than a platform dependency.
- How should I integrate micro-module/enqueue-fs into a Laravel app without locking in?
- Expose the transport behind an application-owned job-dispatch interface, then use a custom Laravel queue connector or a standalone Enqueue consumer command. Start with non-critical jobs such as report generation, cache warming, or local notifications. Run it in parallel or shadow mode behind a feature flag and keep a fallback to database, Redis, or another broker. Avoid spreading package-specific calls through domain code.
- Is micro-module/enqueue-fs actively maintained and supported?
- It has 0 stars, 0 dependents, and an opportunity score of 28.25, indicating negligible community validation, and the repository description marks it read-only. Expect to own the integration and potentially fork the MIT-licensed code. Monitor upstream and pin versions because maintenance risk is high. Do not treat it as a platform dependency without a successful proof of concept and reassessment.