- What is andrey-helldar/blacklist-server used for?
- It is a Laravel package that exposes a lightweight HTTP API for checking values such as IP addresses, emails, and domains against a configurable blacklist. It centralizes blacklist storage and lookup so multiple applications can share one source of truth. It also provides REST endpoints for managing blacklist entries.
- How do I install blacklist-server in a Laravel application?
- Install it with Composer using composer require andrey-helldar/blacklist-server. Laravel package discovery will typically register the service provider automatically; if your app does not use discovery, add the provider manually. Publish the package configuration to customize sources, drivers, and matching rules.
- How do I configure blacklist sources and matching rules?
- Publish the package configuration file and edit the source and matching rule settings for your environment. The package is designed to support custom drivers and storage backends, so you can adapt it to your existing blacklist data. Check the package documentation for the exact configuration keys and driver contracts.
- Which Laravel versions does blacklist-server support?
- The provided overview does not list explicit Laravel version constraints, so verify compatibility in the package composer.json on Packagist or GitHub before adopting it. It is built as a Laravel package with a service provider and publishable configuration. Test it against your application's Laravel version in a staging environment first.
- What API endpoints does blacklist-server expose?
- The package exposes REST endpoints for querying blacklist entries and for managing them. The exact route paths and request payloads should be confirmed in the package routes or documentation for your installed version. You can then call those endpoints from other services to check IPs, emails, domains, or similar identifiers.
- Can blacklist-server block IP addresses, emails, and domains?
- Yes, it is intended for checking identifier values such as IP addresses, emails, and domains against a configurable blacklist. Consuming applications can use the API response to enforce access rules or filter incoming requests. The actual blocking logic remains in your application or gateway, while this package centralizes the blacklist lookup.
- Can multiple Laravel applications share one blacklist?
- Yes, the package is designed to separate blacklist storage and lookup from the applications that consume it. You can run it as a centralized service and have multiple applications query the same API for consistent filtering. This avoids duplicating blacklist data across every service.
- How do I test the blacklist API in Laravel?
- Use Laravel's HTTP testing helpers to send requests to the package routes and assert the JSON responses. If you use custom drivers or storage backends, mock or fake those dependencies in your feature tests. Review the package's own test suite for examples of expected request and response behavior.
- Is blacklist-server suitable for production use?
- It can be suitable for production when deployed as a dedicated Laravel service with appropriate security controls. Protect the management endpoints with authentication and middleware, use HTTPS, and restrict network access to trusted consumers. Also review rate limiting and the reliability of your configured storage backend before relying on it for access decisions.
- What are alternatives to blacklist-server for Laravel blacklist checks?
- Alternatives include checking a local database table directly in each application, using a shared cache or Redis set, or relying on a WAF or firewall service for network-level blocking. This package is a good fit when you want a simple centralized HTTP API that complements Andrey Helldar's blacklist tooling. Evaluate whether your team needs a dedicated service or can reuse existing infrastructure.