Weave Code
Real Estate Laravel Laravel Package
liberu-real-estate/real-estate-laravel
A Laravel package for building real estate applications, with property listings, agents, locations, search, models, migrations, and admin-ready CRUD to help you launch a real estate portal quickly.
Real Estate / Estate Agent, solution for your Property Agency. Application written in Laravel 13 / PHP 8.5 using Filament 5. Support for Rightmove, Zoopla, OnTheMarket
Frequently asked questions about Real Estate Laravel
- How do I install liberu-real-estate/real-estate-laravel in a Laravel application?
- Install it through Composer with composer require liberu-real-estate/real-estate-laravel, then run the package migrations and publish its config files. Because it is an opinionated domain module, expect published config, database migrations, Eloquent models and Filament or Livewire admin surfaces. Review the published config and migration set before running them against any existing database.
- Which Laravel and PHP versions does this real estate package support?
- The repository describes the package as built on Laravel 13, PHP 8.5 and Filament 5. Exact Composer constraints for a given tag, such as v9.0.0, are not published in the release notes, so check composer.json or Packagist before committing. If your application runs an older Laravel or PHP release, verify the floor requirements first because that is the single gating factor for adoption.
- Does the package support Rightmove, Zoopla and OnTheMarket integrations?
- Yes, the package advertises support for Rightmove, Zoopla and OnTheMarket alongside its property listings. Treat these as feed or listing syndication integrations and confirm in the source whether they are first-party implementations or thin wrappers you would own. Portal feed formats change, so budget time for regression testing against each portal's schema.
- Can I use this as a full property portal or just as a headless data layer?
- It is designed as a real estate application module, so it ships listings, agents, locations, search, models, migrations and admin-ready CRUD you can run largely as-is. That makes it a strong fit for launching a portal quickly, and a weaker fit if you already own a mature property schema. If you only need listings, you can consume the models and migrations headlessly, but you inherit the full schema either way.
- Will the package migrations conflict with my existing property or listing tables?
- Likely yes if you already have a property schema, because the package brings its own migrations, models and relationships. The cost then shifts from integration to reconciliation and avoiding dual writes to two property tables. Audit the migration filenames, table names and column definitions before installing, and plan a mapping or rename strategy rather than running migrations blind.
- Does it include Filament admin panels and CRUD out of the box?
- The package targets Filament 5 and advertises admin-ready CRUD for its domain entities, so expect resource pages for listings, agents and locations. Confirm which Filament version your application currently runs, since a Filament 5 requirement may force an admin panel upgrade. If you have custom Filament resources, check namespace and panel registration collisions before enabling the package's own panel.
- What are the breaking changes in v9.0.0 and how do I upgrade from v8?
- The v9.0.0 release bundles localized document templates with signing workflow improvements plus an application dependency upgrade. The major version bump is most plausibly driven by raised PHP, Laravel or third-party constraints, though a template or signing contract change cannot be ruled out from the notes. There is no published breaking-change list or upgrade guide, so diff composer.json and the signing code paths yourself before upgrading.
- What happens to in-flight signature requests created under v8 when I upgrade to v9?
- This is the highest-risk area, because signing changes can affect envelope state, provider callback payloads and stored document paths. Localized templates imply new or altered template storage, likely with new migrations and a backfill of existing templates. Test with real in-flight envelopes in staging: verify envelopes still resolve, provider webhooks still parse, and signed documents are still retrievable from their original storage paths.
- Is this package production-ready, and how much test coverage does it have?
- The package is installable via standard Composer and covers a well-understood domain, but there is no indication of a support policy, LTS branch or security disclosure process. Both changes in v9.0.0 come from a single contributor, so bus factor is a real concern. Build your own regression harness around document rendering and signing state transitions rather than relying solely on the package's suite.
- How is the package maintained, and what alternatives should I consider?
- Release notes name two PRs and no migration guide, so cadence and long-term support commitments are unclear; ask the maintainer directly about a security contact and CVE history. For alternatives, weigh it against general Laravel CRUD and admin starters paired with your own listing schema, or a dedicated property CRM if you need deep portal syndication. Choose this package when its opinionated property schema and Filament admin surface match your project closely enough to adopt as-is.
Weaver
How can I help you explore Laravel packages today?