- How do I install modularsoftware/laravel-gedcom in a Laravel application?
- Install it with Composer using composer require modularsoftware/laravel-gedcom. As a Laravel package it is expected to support service-provider auto-discovery and a small configuration surface, but verify the README for any publishable config or migration steps. Run the package's tests or a small import spike before wiring it into production code.
- Which Laravel and PHP versions are supported by modularsoftware/laravel-gedcom?
- The current Composer constraints in the package are the source of truth, so check them before upgrading Laravel or PHP. Because the last release noted in the evaluation is January 2023, compatibility with the newest Laravel and PHP releases should be treated as an explicit gate. Run composer why-not against your target framework version and test on the exact runtime matrix you deploy.
- Does laravel-gedcom import GEDCOM data directly into Eloquent models?
- The package overview says it parses GEDCOM files and loads them into an object-oriented model of individuals, families, events, and sources, and that it can import them into Laravel. It does not clearly promise that parsing writes directly to your application's Eloquent models. Plan to map parsed records through your own DTOs or import services so the package does not become your canonical domain model.
- Can I export GEDCOM 5.5.1 files from Laravel with this package?
- Yes, the package description states that it can export GEDCOM 5.5.1 files from Laravel. For production use, generate exports from your application's canonical data and validate the resulting files against an external GEDCOM consumer. Do not rely only on the package's own parser as proof that the export is interoperable.
- How does laravel-gedcom handle large GEDCOM files and memory usage?
- The provided overview does not specify whether the parser streams records or loads the full document into memory. Before importing large files, test with representative datasets and monitor memory and execution time. Run parsing in queued jobs, store original uploads immutably, and enforce upload size and resource limits.
- What GEDCOM encodings and malformed files does laravel-gedcom support?
- The overview does not document the package's handling of encodings such as UTF-8 or ANSEL, malformed lines, custom tags, or unresolved references. GEDCOM files vary by exporter and dialect, so build a fixture suite that covers the files you actually expect. Capture parse errors and validate imports before persisting records.
- How should I validate relationship integrity after importing GEDCOM data with laravel-gedcom?
- Treat the parsed GEDCOM structures as input data and validate them against your application's rules before persistence. Check that family links, individual references, events, and source citations resolve correctly, and reject or quarantine records with broken references. A staging table or DTO layer makes it easier to review and correct relationship issues before they reach production entities.
- Is modularsoftware/laravel-gedcom actively maintained and safe for production?
- The evaluation notes a small community, 22 stars, and a last release in January 2023, so ongoing maintenance is a real risk. Security risk is described as low if the package only parses files, but uploads and parser resource consumption still need controls. Use it behind an internal adapter, pin compatible versions, and have a fork or replacement plan.
- How do I test GEDCOM import and export in a Laravel application using laravel-gedcom?
- Create fixture files that cover UTF-8 and legacy encodings, large files, malformed records, custom tags, and relationship-heavy datasets. Test both parsing and export validation in CI on the Laravel and PHP versions you deploy. Keep package calls behind GedcomImporter and GedcomExporter interfaces so tests can focus on your mapping and validation logic.
- What are alternatives to laravel-gedcom for reading GEDCOM files in Laravel?
- Alternatives include standalone PHP GEDCOM parsers, custom import adapters, or a forked or wrapped version of this package if it lags your framework. The right choice depends on whether you need GEDCOM 5.5.1 export, streaming for large files, and support for specific exporter dialects. Keep the parser behind an interface so you can replace it without changing your domain model.