- Can I install sgl/flts-bundle in a Laravel application?
- No. sgl/flts-bundle is a Symfony2 bundle, not a Laravel package, and it does not ship a Laravel service provider, package discovery metadata, migrations, or Eloquent models. It relies on Symfony bundle conventions, dependency injection, routing, security, and likely Doctrine ORM patterns that do not map cleanly onto Laravel. Treat it as a reference artifact rather than a Composer dependency in a Laravel project.
- What is sgl/flts-bundle actually used for?
- It is a Symfony2 bundle providing a freelancer timesheet and billing application, covering time tracking, rates, approvals, and invoice generation. The domain concepts are useful if you need freelancer billing workflows. The implementation, however, is tightly coupled to Symfony2 rather than Laravel.
- Does sgl/flts-bundle support Laravel 10, 11, or 12?
- There is no evidence of support for any modern Laravel version. The last release dates to 2018-02-22 and targets the Symfony2 line, which is long past end of life. Modern Laravel requires current PHP versions and framework APIs that this bundle predates, so you should assume incompatibility.
- Is sgl/flts-bundle still maintained?
- No active maintenance is visible. The last release was 2018-02-22, the project has around 12 stars and zero dependents, and there is no vendor support or community signal indicating production use. If you fork it or put it into production, your team owns security patching, PHP and Symfony upgrades, and billing-rule correctness.
- Why does sgl/flts-bundle fail to install or boot in a modern PHP project?
- Expect Composer constraint conflicts from old Symfony and PHP requirements, followed by container, routing, security, and session conflicts if installation succeeds. The bundle predates modern PHP type systems and current Composer constraint practices. Even a Doctrine bridge or Symfony compatibility layer would add complexity and risk without strategic value.
- How do I install sgl/flts-bundle with Composer?
- Installation would only make sense inside a Symfony2 application, where bundles are registered in the kernel and configured through Symfony's container. In Laravel, composer require will not register routes, service providers, or migrations automatically, so nothing works out of the box. Do not add it to a Laravel composer.json as a production dependency.
- Can I reuse the business logic or domain model from sgl/flts-bundle in Laravel?
- Yes, but only as a reference. Run a time-boxed spike to document its entities, timesheet approval states, rate logic, and invoice generation behavior, then reimplement the required subset as a Laravel-native module. Extracting the domain model avoids importing the Symfony implementation and its framework coupling. Define Laravel-native acceptance criteria and a data model before writing code.
- What should I verify before trusting sgl/flts-bundle billing calculations in production?
- Verify the source license is permissive and compatible with commercial use, and confirm the exact PHP and Symfony versions and dependencies required. Review the tax, rate, invoice, and time-rounding rules against your target market, because billing-calculation defects are a stated risk and there is no visible test coverage. Validate billing outputs in parallel against the existing system before cutover.
- How do I migrate an existing Symfony2 app that uses sgl/flts-bundle to Laravel?
- Do not embed the bundle in Laravel. Isolate the existing Symfony2 system behind an API and migrate incrementally, starting with a thin vertical slice covering clients, projects, time entries, rates, approvals, and invoices. Move legacy data through a controlled mapping and validate billing outputs in parallel. Decommission the legacy dependency only after the Laravel-native module passes acceptance criteria.
- What are the alternatives to sgl/flts-bundle for timesheet and billing in Laravel?
- Build a Laravel-native module using Eloquent models, migrations, policies, and queued jobs, or evaluate a maintained Laravel or PHP billing package with active releases and test coverage. The key requirements are current PHP support, Laravel package discovery, and documented tax and rate rules. Either path avoids inheriting an abandoned Symfony2 codebase and its scaling unknowns.