Weave Code
Geo Ip Bundle Laravel Package
ndevs-eu/geo-ip-bundle
A Symfony bundle for IP-based geolocation with MaxMind GeoIP2. Detect visitor country, locale, and currency from IP addresses, configure database paths, and use Twig helpers for geo-aware routing, redirects, and localized content.
Symfony bundle for Geo IP functionality
Frequently asked questions about Geo Ip Bundle
- What does ndevs-eu/geo-ip-bundle do?
- It is a Symfony bundle that adds IP-based geolocation using MaxMind GeoIP2. It can resolve a visitor's country, locale, and currency from an IP address and exposes a typed GeoResponse value object. The bundle also provides configurable database paths and Twig helpers for geo-aware routing, redirects, and localized content. That makes it useful when pricing, tax, compliance, or content decisions depend on country-level context.
- Is ndevs-eu/geo-ip-bundle compatible with Laravel?
- The package is built as a Symfony bundle, not a Laravel-native Composer package, so it does not publish Laravel version constraints and is not a drop-in replacement for Laravel's service providers or facades. You can still reuse the underlying GeoIP2 logic or adapt the GeoResponse concept behind your own Laravel service or interface. If you need zero-glue Laravel support, evaluate Laravel-specific GeoIP alternatives first. For teams already comfortable with Symfony components, the integration effort is usually modest.
- How do I install and configure the GeoIP database path?
- Install it with Composer using the package name ndevs-eu/geo-ip-bundle, then register the bundle in your Symfony application. You configure the MaxMind GeoIP2 database path so the bundle can resolve IPs locally rather than depending on a network call. Keep the database file outside version control and point each environment at its own copy, because country resolution can diverge if a developer's local database is stale compared with production.
- How do I detect country, locale, and currency from an IP address?
- Resolve the request IP through the bundle's geo service, which returns a GeoResponse value object. Recent versions expose countryName and countryIsoCode, so you can use the ISO 3166-1 alpha-2 code as a stable key for pricing, tax, or routing logic instead of matching display names. Locale and currency fields can then drive localized content or redirect rules. Always treat the result as country-level context, not precise location.
- What are countryName and countryIsoCode in GeoResponse?
- They are additive fields added in v1.0.16 to the GeoResponse value object. countryName is the human-readable display name, while countryIsoCode is the ISO 3166-1 alpha-2 code such as US or DE. The ISO code is the more useful field for downstream joins, tax rules, and feature flags because it avoids fragile string matching against country names. The change is non-breaking under semantic versioning, so existing consumers continue to work.
- Can I test geo-IP logic without hitting a live database or network?
- Yes, but you need to confirm the package exposes a seam for injecting a fake or fixture-backed resolver. If it queries a third-party network service, tests that exercise GeoResponse can become environment-dependent unless you stub the service. Prefer local MaxMind database mode for deterministic tests, and assert against fixed IP-to-country fixtures. Wrap the bundle behind your own interface so your application tests do not depend on vendor response shape.
- Is IP geolocation GDPR compliant?
- IP-to-country is generally less sensitive than IP-to-precise-location, but IP addresses are still treated as personal data under GDPR and CCPA in many readings. You should know whether the bundle persists IPs, whether it calls a third-party service, and whether a local-database mode avoids egress. Document the lawful basis, retention, and vendor data-processing terms before using it in production. Country-level resolution alone is usually easier to justify than precise geolocation.
- Does the bundle make network calls or use a local MaxMind database?
- The blurb describes MaxMind GeoIP2 with configurable database paths, which points to local database resolution rather than a mandatory network service. The important production question is whether any optional remote lookup exists and how it is configured. Local database mode reduces latency and third-party availability risk in hot request paths. Confirm the behavior in your environment before relying on it for pricing or tax logic.
- How often should I update the GeoIP database?
- MaxMind databases change over time, so schedule regular refreshes and keep development, staging, and production on the same version. Country-level data is relatively stable, but stale databases can still produce silent behavioral divergence in pricing, tax, or redirect rules. Treat the database as a deployable artifact with a version and refresh policy rather than a one-time download. If your product redistributes geo data, also review MaxMind's attribution and licensing terms.
- What are the Laravel alternatives to this Symfony GeoIP bundle?
- Laravel teams often choose Laravel-specific GeoIP packages or wrap a MaxMind reader directly in a service class. A dedicated Laravel package may give you a service provider, facade, and test fakes with less glue than a Symfony bundle. The trade-off is that this bundle's typed GeoResponse and Twig helpers are useful if you already use Symfony components or need its routing conveniences. Compare database update policy, privacy posture, and testability before switching.
Weaver
How can I help you explore Laravel packages today?