- Is atoolo/citygov-bundle a Laravel package?
- No. atoolo/citygov-bundle is a Symfony bundle from Sitepark's Atoolo/CityGov product line, and it registers itself through Symfony mechanisms such as Kernel::registerBundles(), DI compiler passes, service tags and a bundle-level config tree. Laravel's container and package discovery do not understand any of that. It is published by the vendor for CityGov/Atoolo deployments, not as a framework-agnostic library.
- Can I install atoolo/citygov-bundle in a Laravel application with Composer?
- Composer will resolve and download it because the license is MIT and the PHP constraint (8.1 to 8.4) likely matches, but nothing will be auto-wired. There is no Laravel service provider, no facade and no config publish step, and the useful classes are entangled with Symfony contracts (EventDispatcher, Config, DependencyInjection) and Atoolo interfaces. A direct port means shimming the Symfony substrate yourself while inheriting every upstream coupling, which is not recommended.
- What does atoolo/citygov-bundle actually do?
- It is an enrichment and integration layer that turns CityGov content objects into Solr index documents and exposes CityGov features over GraphQL, including online services, teaser features and person search/suggest. It is not a standalone capability: value only appears once you already run CityGov content and Atoolo search. Think of it as the glue between municipal content, the Solr index and a GraphQL query surface.
- What are the runtime requirements for this bundle?
- You need a Symfony application with the Atoolo stack, specifically atoolo/search-bundle pinned at ^1.14.0 as of v1.5.0, plus a SiteKit schema namespace (SiteKitSchema2x), resource and link-factory abstractions, and a Solr instance configured with Atoolo field conventions such as sp_meta_string_leikanumber and startletter. Without that substrate the bundle has nothing to work against. Plan for a full Symfony deployment or sidecar, not a drop-in library.
- Which PHP versions does atoolo/citygov-bundle support?
- The CI matrix covers PHP 8.1 through 8.4, with 8.1 flagged as no longer checked automatically in the README badges. PHP 8.2, 8.3 and 8.4 are the actively validated versions. There is no Laravel version support of any kind because the package targets Symfony, so Laravel compatibility is your own responsibility if you attempt it.
- What is the best way to integrate CityGov with a Laravel application?
- Run CityGov/Atoolo as a separate Symfony service and let Laravel act as the product surface (auth, UX, citizen workflows, admin), talking to it only over HTTP/GraphQL. This sidecar pattern gives the highest fidelity and lowest risk: no shared container, no PHP-level coupling and no Composer cross-contamination. The alternative is to mine the Solr field mapping and GraphQL schema and reimplement natively in Laravel, which is more effort but removes vendor coupling entirely.
- Is atoolo/search-bundle or Solr optional for this bundle?
- Treat them as hard runtime dependencies. The bundle pins atoolo/search-bundle at ^1.14.0 and its core job is enriching documents with Solr field conventions, so removing the search bundle or Solr leaves it with no meaningful behaviour. If you only want CityGov data in Laravel, query the Symfony service instead of trying to detach the enrichment pipeline.
- Is the CityGov GraphQL schema stable enough to generate a Laravel client from?
- The README does not publish an SDL or supergraph contract, so codegen against it is a discovery task rather than a given. Ask the vendor whether a stable published schema exists and how schema breaks are communicated before committing to generated types. If no contract is guaranteed, hand-write a thin GraphQL client and validate against a reference deployment first.
- How actively maintained is atoolo/citygov-bundle?
- It ships fast but is effectively a single-vendor, low-adoption package: six minor releases from 1.0 to 1.6, zero stars, zero dependents and a bus factor of one organisation. Several bumps are breaking-adjacent, such as the search-bundle ^1.14.0 pin and a phone number field change in 1.5.0, so expect to track upstream closely. The metadata also lists a last release date of 2026-06-03, which is a data-integrity anomaly worth flagging before you rely on release cadence.
- What license does atoolo/citygov-bundle use and is the code quality good?
- It is MIT licensed, so commercial use and forking are permitted. Engineering hygiene is better than typical for a zero-star repository: PHPStan level 9, Codecov coverage reporting, a PHP 8.1 to 8.4 CI matrix, an external end-to-end suite (atoolo-e2e-test) and conventional-commit changelogs. What it lacks is community adoption, so vet the support contract and LTS policy with Sitepark directly.