Weave Code
Tomato Locations Module Laravel Package
tomatophp/tomato-locations-module
Tomato Locations is a ready-to-use module for TomatoPHP that adds full location management to your Laravel admin panel, letting you manage countries, cities, areas, and related data with a clean Filament interface, migrations, and seeders out of the box.
Database seeds for Locations plugin for TomatoPHP
Frequently asked questions about Tomato Locations Module
- What is tomatophp/tomato-locations-module used for?
- It is a TomatoPHP module that adds location management to a Laravel admin panel, letting you manage countries, cities, areas, and related data. It ships with migrations, seeders, and a Filament interface so geographic reference data is available out of the box. It is best suited to Laravel applications that need standardized location data for addresses, customers, warehouses, or orders.
- How do I install tomato-locations-module in a Laravel project?
- Install it with Composer using composer require tomatophp/tomato-locations-module, then rely on Laravel package discovery or register the service provider manually if needed. Publish the package config, migrations, and seeders, run the migrations, and seed the location data. Because this is a v1.0.0 release, do the install in a sandbox first and pin the version before using it in production.
- Which Laravel and PHP versions does Tomato Locations support?
- The published overview does not list explicit Laravel or PHP version constraints, so check the package composer.json and the linked changelog before installing. Verify compatibility against your exact Laravel and PHP versions in a test environment. If the constraints are too narrow for your stack, evaluate whether an older Laravel branch or an internal patch is required.
- Does this package require TomatoPHP core or Filament?
- Tomato Locations is part of the TomatoPHP ecosystem and provides a Filament admin interface, so it likely expects TomatoPHP conventions and Filament to be present. For a plain Laravel app without TomatoPHP, treat standalone use as unconfirmed until you review the service provider and dependencies in a sandbox. If the admin layer is tightly coupled, you may only be able to reuse the models, migrations, and seeders.
- What location entities and data does the module include?
- The overview states it covers countries, cities, areas, and related data through migrations and seeders. Postal codes, timezones, regions or states, and translation tables are not confirmed, so inspect the migration and seeder files directly. Also confirm the source, license, and refresh process for the seeded location data before relying on it as governed reference data.
- Does tomato-locations-module provide admin CRUD screens or API routes?
- It advertises a Filament admin interface for managing locations, which implies CRUD resources inside a TomatoPHP admin panel. Whether it also exposes REST API routes or only models and migrations is not documented in the overview. Check the package routes and service provider to see what surfaces are available to your frontend or integrations.
- How do I seed the location data and how long does seeding take?
- Publish the package seeders and run them with php artisan db:seed or a targeted seeder class after migrating. City-level datasets can be large, so measure seed runtime in staging on your target database engine rather than assuming it is fast. Use transactions, chunked inserts, and a maintenance window if the seed volume is significant.
- Is tomato-locations-module production-ready at version 1.0.0?
- Version 1.0.0 is an initial release with limited published detail, and test coverage is not stated, so treat it as unproven for production. Review the migrations for reversibility, back up before running them, and keep a rollback plan. Pin the exact version and monitor upstream releases if location data or schema stability matters to your application.
- Does it support non-English city and country names and localization?
- Localization support is not described in the overview, so check whether the schema uses translation tables, JSON columns, or plain name fields. Test UTF-8 values and collation behavior on MySQL or PostgreSQL with real non-English location names. If translations are missing, you may need to extend the schema or maintain your own localized labels.
- What are the alternatives to Tomato Locations for Laravel?
- Alternatives include standalone country, state, and city data packages for Laravel, importing a public geo dataset with your own seeders, or calling a geocoding API at runtime. Compare them on data license, update cadence, localization, and whether you need Filament admin screens. Tomato Locations makes the most sense if you are already building on TomatoPHP and want the admin UI included.
Weaver
How can I help you explore Laravel packages today?