Weave Code
Sic Bundle Laravel Package
gepur-it/sic-bundle
gepur-it/sic-bundle is a PHP bundle for integrating SIC functionality into Symfony applications. It packages configuration and service wiring so projects can add SIC-related features with minimal setup and keep integration code organized.
Single Instance Console Command Bundle
Frequently asked questions about Sic Bundle
- Is gepur-it/sic-bundle compatible with Laravel?
- No. It is a Symfony bundle with a Bundle class and DependencyInjection extension, while Laravel has no bundle registration or Symfony services.yaml autodiscovery. Installing it in a Laravel application will not make it work.
- Which Laravel versions can use gepur-it/sic-bundle?
- It can only co-resolve with Laravel 8 or earlier because v6.0.0 pins Symfony 5. Laravel 9 requires Symfony ^6.0, Laravel 10 requires ^6.2, and Laravel 11/12 require ^7.0. Laravel 8 has been end-of-life since January 2023.
- How do I install gepur-it/sic-bundle in Laravel?
- You should not expect a supported installation path. The package expects Symfony bundle registration and container configuration, not a Laravel service provider. A Laravel port or fork would be required, and Composer installation alone is not enough.
- What PHP versions does gepur-it/sic-bundle support?
- Version 6.0.0 adds a PHP 8 floor in Composer, correcting older claims that no PHP 8 support was declared. The supplied context does not show a tested PHP 8.2, 8.3, or 8.4 matrix or CI evidence. Treat support as declared at a minimum, not verified across modern PHP versions.
- What is gepur-it/sic-bundle used for?
- It packages SIC integration for Symfony applications through bundle registration, a configuration tree, and service container wiring. Its functional intent includes a Single Instance Console Command, which is a per-command mutex or overlap guard. That guard is a small concern rather than a full architectural component.
- Does gepur-it/sic-bundle support Symfony 6 or Symfony 7?
- No. Version 6.0.0 sets a Symfony 5 Composer constraint, and Symfony 5.4 is at or past the end of security support. The release note does not explain whether the code is actually incompatible with modern Symfony Console or what the blocker is. Modern Symfony 6 and 7 are not supported by this constraint.
- Is gepur-it/sic-bundle actively maintained?
- The maintenance signal is weak. v6.0.0 is a single-commit constraint bump after a roughly five-year gap, with no feature work, behavioral changelog, security fix, or test/CI signal. The package still shows 1 star, 0 dependents, and no evidence of a supported-version policy or security-response process.
- How does the Single Instance Console Command lock work?
- The supplied context does not document the lock backend or semantics. It is unknown whether the lock uses filesystem, symfony/lock, database, or a PID file, and whether it has a TTL or releases on SIGTERM/SIGKILL. Fail-open versus fail-closed behavior and per-argument key scoping are also unreviewed, so stale-lock correctness cannot be assumed.
- What are Laravel alternatives to gepur-it/sic-bundle?
- For a Laravel console overlap guard, use Laravel scheduler withoutOverlapping, cache locks, or a small custom mutex around the command. symfony/lock can also be used directly if its semantics fit the job. These avoid adopting a Symfony 5 bundle into an unsupported Laravel 8 stack.
- Can I use gepur-it/sic-bundle in production?
- It is high risk for a Laravel production app. Adoption would start on EOL Laravel 8 or earlier plus Symfony 5 with an expired security-support window, inheriting unpatched dependency trees. The absence of release discipline, tests, and documented lock semantics makes silent cron-guard failure a real concern.
Weaver
How can I help you explore Laravel packages today?