- What is liquetsoft/fias-symfony used for?
- liquetsoft/fias-symfony is a Symfony bundle for importing and querying the Russian FIAS address database. It provides Doctrine entities and repositories, console commands for loading official address data, and hierarchical address search for autocomplete or validation. In a Laravel app, its main value is the underlying FIAS importer core, not the Symfony bundle layer.
- Can I use liquetsoft/fias-symfony in a Laravel application?
- Not as a drop-in Composer package. The package is built on Symfony bundle machinery such as a Bundle class, DI extension, compiler passes, and Symfony console commands, while Laravel does not ship FrameworkBundle or a Symfony kernel. You would either extract and wrap the core importer in a Laravel service provider and Artisan command, or run the bundle as a separate Symfony import worker. Both approaches take days to weeks, not hours.
- What are alternatives to liquetsoft/fias-symfony for Laravel address lookup?
- For Laravel, the practical alternatives are to use the vendor's underlying FIAS core library directly with a thin Laravel wrapper, or to run a small Symfony sidecar worker that owns imports while Laravel reads the resulting tables. Building a custom importer against official GAR or FIAS distributions is another option if you need full control over schema and updates. Evaluate whether each option supports GAR, incremental updates, and your target database before committing.
- How do I install and configure liquetsoft/fias-symfony in Symfony?
- In Symfony, installation is typically done with composer require liquetsoft/fias-symfony and registering the bundle in the kernel. You then configure the Doctrine entity mapping and database settings, run the provided console commands to import FIAS data, and query addresses through the bundle's repositories. The overview does not document exact configuration keys, so verify them against the repository README and source.
- Does liquetsoft/fias-symfony support Laravel 11 and PHP 8?
- The package itself is a Symfony bundle and does not target Laravel 11 or any Laravel version. Laravel includes some Symfony components, but not FrameworkBundle or the bundle auto-registration and compiler-pass container behavior this package relies on. PHP version compatibility must be checked against the package's composer.json; the overview does not state supported PHP or Symfony versions.
- Does liquetsoft/fias-symfony support GAR or only legacy FIAS data?
- The technical evaluation flags this as the most important question: FIAS is the legacy Russian address registry, while the state has moved to GAR with different schema, formats, and APIs. The package overview describes FIAS integration but does not state whether the underlying core supports GAR or only deprecated FIAS dumps. Confirm this with the maintainer and inspect the core library before relying on it.
- Does liquetsoft/fias-symfony support incremental FIAS updates?
- The overview does not document delta or incremental import support. The evaluation notes that you must determine whether the core supports incremental updates or only full reloads, because that decides your steady-state operational cost. If only full reloads are supported, schedule and size the import process accordingly.
- How large is a full FIAS import and which databases are supported?
- A full FIAS or GAR import is operationally large: the evaluation describes tens of gigabytes compressed and hundreds of millions of rows across address, house, and hierarchy tables. The overview does not name supported database engines, so verify MySQL or PostgreSQL support, bulk-load requirements, and any superuser-level operations in the repository. Plan staging tables, indexing, and a read model so Laravel does not traverse the full hierarchy per request.
- Is liquetsoft/fias-symfony actively maintained and safe for production?
- Adoption is very low: the evaluation notes 27 stars, zero dependents, and effectively one maintainer. The 2025-05-11 release shows recent activity, but activity does not equal edge-case coverage for a large, schema-unstable government dataset. Treat it as a component you may need to fork or maintain yourself, especially through the FIAS-to-GAR transition.
- How should I test a Laravel integration with FIAS data?
- Use a small fixture subset of FIAS data instead of a full import for routine tests. Cover hierarchy traversal, autocomplete queries, missing or duplicate address objects, and the schema your Laravel app reads. If you wrap the core importer, add integration tests for the import command and a smoke test against your production database engine.